-
Notifications
You must be signed in to change notification settings - Fork 55
feat: forbid write apis when resources are managed by gateway #917
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
Conversation
@bzwei How do these remote resources get cleaned up once they are in the EDA Database? If there is no delete would there be some system task that will do periodic checks to cleanup resources by synchronizing with the Gateway. {{ GATEWAY_HOST }}/api/v1/organization/15 So in or database we can have references to external objects and not copies. As soon as we start storing copies we have to worry about it going stale. With references we only have a link in our database. I am guessing eventually the Credentials and Credential Types will also end up as a Remote Resource and when the UI wants to attach them to the Activation it would get the current list from the Gateway and then use a link in our database. When the workers start activation they will make a REST API call to fetch the Credential and Credential Types and do the appropriate things with it and send the data to ansible-rulebook. |
911be1a
to
fdfa053
Compare
|
forbid create/update/delete organzation, team, user apis when DIRECT_SHARED_RESOURCE_MANAGEMENT_ENABLED is True AAP-24301: Update 2.5 EA EDA API to error on endpoints that correspond to gateway-managed resources
fdfa053
to
accb03e
Compare
Link companion patch ansible/awx#15234 |
forbid create/update/delete organzation, team, user apis when DIRECT_SHARED_RESOURCE_MANAGEMENT_ENABLED is True
AAP-24301: Update 2.5 EA EDA API to error on endpoints that correspond to gateway-managed resources