Using client_id/client_secret from client created by this tool, in this tool

[thyming]

Describe the problem you'd like to have solved

I would like to be able to use client id/client secret from a client I create with this tool as secret values in an Auth0 action (also created by this tool). Without this ability, these values have to be copied from the console after a run of the cli.

Describe the ideal solution

something like

secrets:
  - name: auth0_client_id
     value: &my_m2m_client.client_id
  - name: auth0_client_secret
     value: &my_m2m_client.client_secret

Alternatives and current work-arounds

I may be mistaken, but the only alternative I see right now involves fetching the client details out of band of this tool, via the console or another api call, and injecting that as a variable into the config.

Additional context

No additional context.

[willvedd]

Agreed that something like this would be quite nifty. However, supporting it sounds quite complex. Just thinking through some basic cases, we'd need be very careful about the ordering of API calls and create some type of syntax to identify resources by their name instead of ID, which isn't always unique. The workaround you described is exactly how I'd accomplish this, albeit not as elegant as the ideal approach you've described. I'm ok with keeping this ticket open to gather more feedback, but realistically this isn't something we'd likely support anytime soon.

Perhaps some it's some consolation, but if I'm not mistaken, you should be able to accomplish this with the Auth0 Terraform Provider's client data source. It might be worth looking into that if this type of functionality is required in your workflows.

[charliearaya]

Im in need of the same thing. In some cases I want to be able to store some application ID inside a custom action.