Allow deeper structure in keyword replacements #1083
Description
Checklist
- I agree to the terms within the Auth0 Code of Conduct.
Describe the problem you'd like to have solved
We have created different tenants for our environments as described in the documentation to set up multiple environments. Our Auth0 applications have different callback and logout URLs depending on the environment, e.g. for local development we'd have something as http://localhost:9000/callback while in production it would be https://my-application.domain.com/callback.
The documentation describes keyword replacements as a shallow object with only one level of hierarchy which for many applications leads to a very large list of keys.
Describe the ideal solution
It would be really nice to extend this structure to a deep object so the definition could be something similar as:
"AUTH0_KEYWORD_REPLACE_MAPPINGS": {
"APPLICATION_1": {
"CALLBACK_URLS": ["http://localhost:9000/callback"],
"LOGOUT_URLS": ["http://localhost:9000/logout"],
}
}
They could then be referenced as e.g. @@APPLICATION_1.CALLBACK_URLS@@.
Alternatives and current workarounds
Our current configuration looks as follows:
"AUTH0_KEYWORD_REPLACE_MAPPINGS": {
"APPLICATION_1_CALLBACKS_URLS": ["http://localhost:9000/callback"],
"APPLICATION_1_LOGOUT_URLS": ["http://localhost:9000/logout"],
"APPLICATION_2_CALLBACKS_URLS": ["http://localhost:8888/callback"],
"APPLICATION_2_LOGOUT_URLS": ["http://localhost:8888/logout"],
...
}
Additional context
No response