Create fully idempotent Management API

Feedback
1

The current Management API is only partial idempotent. E.g. resourceServer. If you create the resourceServer again, it can update everything except the audience. Another example is custom domain. This one is not idempotent.

Use-case: We’re using Pulumi to set up Auth0 as IaC. For that, it would be really useful if the resources can be fully idempotent updated. Think about your domain URLs. You could do this simply by changing one central config, and IaC would update all relevant resources (Auth0, DNS etc.). This would make such changes fast and reduce the risk of this change to a minimum.

2

Hi there @micha.mailaender welcome to the community, and thanks for the feedback! Let’s hope this gets some votes from other community members as our team monitors and values community based feedback :chart_with_upwards_trend: :smile:

1 Like
3

It’s got my vote. Being able to call the create user endpoint with an idempotency key would be amazing in AMQP and microservice environments rather than having to call “Get user by email” then only create if not exists.

Saves API calls, helps avoid rate limits, etc. Seems like a win-win