Feature Request: Expand auth0 tenants to output CLI's active tenant domain

[evansims]

Checklist

• I agree to the terms within the Auth0 Code of Conduct.

Describe the problem you'd like to have solved

While recently updating our quickstart guides to use the CLI, I noted an area of improvement that would be great to address.

It would be helpful if the auth0 tenants command could be expanded to offer an option to output the CLI's currently configured active/default tenant domain.

For example, we have auth0 tenants use ... but there isn't a command to return what that assigned tenant is after the fact.

In our quickstart guidance, we direct our users to export the responses from auth0 app create and auth0 api create steps using the --json flag. We pipe the output to .auth0.app.json and .auth0.api.json files, which an SDK can read from to configure itself. This saves end users a lot of time and avoids the error-prone .env editing process, where typos and confusion are frequent.

By further offering a auth0 tenants current type command, or expanding auth0 tenants list with a --current and/or --json flag that exposes a property that identifies the active tenant, we could direct users to use this command to configure the SDK with the appropriate tenant domain as well, without the manual need of looking it up.

Note: At present, the Laravel SDK works around this need by parsing the JSON output of the auth0 app response and extracting the subject from the first signing_keys array property. It massages the data a bit to be useful in the process. This works, but I'm sure there are edge cases where it might not, and it feels a bit hacky. A "real" command for doing this would be great!

Describe the ideal solution

Support a auth0 tenants current type command, or expand auth0 tenants list with a --current flag (or a --json flag, and expose a property on the resulting array that identifies the CLI's actively configured tenant to use.)

Alternatives and current workarounds

No response

Additional context

No response

[andychiare]

+1 on this request.
I'm currently working on integrating our .NET templates with the CLI and faced the same issue. I used @evansims' workaround to get the current domain for applications, but it doesn't work for API registration. So I needed to use a different approach for APIs.
A builtin feature would be very helpful.

[willvedd]

@evansims @andychiare, with v1.3.0, we added a visual indicator to auth0 tenants list to show the active tenant.

It's not exactly the desired implementation, but it achieves a similar result IMO. Please advise if I can close or if a auth0 tenants current is still necessary.

[andychiare]

Hey @willvedd, thank you for your follow up.
The new feature is just a visual indicator while I use the CLI programmatically via JSON responses. In summary, this does not help. I think we still need a specific flag for the current tenant that can be used in combination with the --json flag.