-
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
Add config to exclude Actions - AUTH0_EXCLUDED_ACTIONS #397
Comments
Thanks for raising this. The ask is certainly reasonable, exclusion of any resource is an important tool for devs to express their specific needs. While an easy patch here would to add a IMO, exclusions should be a first-class feature in this tool and we deem it a relatively high priority for this project. However, no promises on if it makes the roadmap right away. Point being, this is something we're thinking about quite a bit here at Auth0! |
@MGough I've raised a proposal for excluding resources that may solve this issue. It would be great to receive your feedback since your use case relies upon excluding certain resources. |
Thanks for letting me know @willvedd I'll try to take a look and leave a comment or a reaction once I've had a think, although it might not be until the end of this week. I've found actions to be a bit of an anomaly in terms of how to exclude them (due to the action & trigger being separate) so I might have some comments or clarifications. |
Shouldn't this be closed since we have this ongoing? #451 |
Describe the problem you'd like to have solved
Auth0 is pushing a move from Rules to Actions, but there's no way to exclude actions from being imported/exported using the Deploy CLI
Describe the ideal solution
Similar to the
AUTH0_EXCLUDED_RULES
there should be aAUTH0_EXCLUDED_ACTIONS
config value.Alternatives and current work-arounds
Continuing to use Auth0 Rules instead of actions
Additional context
Other example of 'exclude' configs exist, but actions is missing: https://auth0.com/docs/deploy-monitor/deploy-cli-tool/import-export-tenant-configuration-to-yaml-file#example-configuration-file
The text was updated successfully, but these errors were encountered: