-
Notifications
You must be signed in to change notification settings - Fork 159
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
Ability to exclude objects when import/export using deploy-cli #394
Comments
Thanks for opening this issue, it's definitely a reasonable feature to ask for. As I have mentioned in another thread, resources exclusion should be a first-class feature and I'd like to take this opportunity to create a more holistic approach. It's on our roadmap so keep an eye out for it in the future! |
@locscoutbee I've raised a proposal for resource exclusion that may solve this issue. It would be great to receive your feedback since your use case relies upon excluding organizations. |
Thank you @willvedd for your nice proposal! I could not agree more. I am looking forward to seeing this new feature. |
Following up here, as proposed in the above-mentioned resource exclusion RFC, the {
"AUTH0_DOMAIN": "<YOUR_DOMAIN>",
"AUTH0_CLIENT_ID": "<YOUR_CLIENT_ID>",
"AUTH0_CLIENT_SECRET": "<YOUR_CLIENT_SECRET>",
"AUTH0_EXCLUDED": [ "organizations"]
} Please update and give it a go! In the meantime, I'm opting to close this out but feel free to re-open if needed. |
Describe the problem you'd like to have solved
I am having around 10k organizations in auth0 tenant. Using deploy-cli import will be very slow. I just want to update manually on Auth0 Console only for this case.
Describe the ideal solution
The ability to exclude organizations when import or export by adding a settings in config.json
The text was updated successfully, but these errors were encountered: