-
Notifications
You must be signed in to change notification settings - Fork 168
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
fix: Trigger resource force replacement when app id changes #1387
Conversation
@Zuhairahmed Please confirm if this needs a doc update as well. I didn't notice we mention about replacement in other resources. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change LGTM but I think we also need to update the doc
Created docs ticket https://jira.mongodb.org/browse/DOCSP-32245 |
Thanks @maastha and @andreaangiolillo. I added in a simple commit for @zach-carr and team to build off if helpful. Otherwise LGTM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Retroactive LGTM
@@ -10,6 +10,8 @@ description: |- | |||
|
|||
`mongodbatlas_event_trigger` provides a Event Trigger resource. | |||
|
|||
Note: If the `app_id` changes in the mongodbatlas_event_trigger resource, it will force a replacement and delete itself from the old Atlas App Services app if it still exists then create itself in the new Atlas App Services app. See [Atlas Triggers](https://www.mongodb.com/docs/atlas/app-services/triggers/) to learn more. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry about the late review - this looks good. My only suggestion is to add a comma right after "...if it still exists," to break up the sentence a little, but it's not an issue.
Description
This PR addresses issue in #1310 and will enable deletion of trigger from existing app followed by creation of a new trigger in the new app on change of app_id attribute.
Link to any related issue(s): INTMDB-925
Type of change:
Required Checklist:
Further comments