Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The management_api_identifier property is present on auth0_tenant data source but missing from auth0_tenant resource #1034

Open
1 task done
njlr opened this issue Sep 26, 2024 · 1 comment
Assignees
Labels
🌱 feature New feature or request

Comments

@njlr
Copy link

njlr commented Sep 26, 2024

Checklist

Describe the problem you'd like to have solved

The data source auth0_tenant has management_api_identifier, but the resource auth0_tenant does not.

management_api_identifier (String) The identifier value of the built-in Management API resource server, which can be used as an audience when configuring client grants.###

Describe the ideal solution

Add management_api_identifier to the auth0_tenant resource

Alternatives and current workarounds

I suppose you can make a data resource that imports the resource.

Additional context

No response

@njlr njlr added the 🌱 feature New feature or request label Sep 26, 2024
@duedares-rvj
Copy link
Contributor

The resource auth0_tenant is only used to update the tenant setting. The data-source is used to retrieve it.
The management_api_identifier is set via the environment variable used for authenticating the provider. More specifically the AUTH0_DOMAIN env variable.

Since this value is not set by a user, but generated when a tenant is created, auth0_tenant cannot support this field.
Hope that resolves the issue.

I'd still be happy to understand the use case that you might be trying to address.
Thanks!

@duedares-rvj duedares-rvj self-assigned this Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🌱 feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants