Skip to content
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

Merged
merged 2 commits into from
Aug 18, 2023

Conversation

maastha
Copy link
Collaborator

@maastha maastha commented Aug 15, 2023

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:

  • Bug fix (non-breaking change which fixes an issue). Please, add the "bug" label to the PR.
  • New feature (non-breaking change which adds functionality). Please, add the "enhancement" label to the PR.
  • Breaking change (fix or feature that would cause existing functionality to not work as expected). Please, add the "breaking change" label to the PR.
  • This change requires a documentation update
  • Documentation fix/enhancement

Required Checklist:

  • I have signed the MongoDB CLA
  • I have read the contribution guidelines
  • I have added tests that prove my fix is effective or that my feature works per HashiCorp requirements
  • I have added any necessary documentation (if appropriate)
  • I have run make fmt and formatted my code

Further comments

Screenshot 2023-08-15 at 09 43 40

Screenshot 2023-08-15 at 10 01 17

@maastha maastha changed the title appid forceNew fix: Trigger resource force replacement when app id changes Aug 15, 2023
@maastha
Copy link
Collaborator Author

maastha commented Aug 15, 2023

@Zuhairahmed Please confirm if this needs a doc update as well. I didn't notice we mention about replacement in other resources.

@maastha maastha marked this pull request as ready for review August 15, 2023 09:03
@maastha maastha requested a review from a team as a code owner August 15, 2023 09:03
Copy link
Collaborator

@andreaangiolillo andreaangiolillo left a 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

@maastha
Copy link
Collaborator Author

maastha commented Aug 15, 2023

on change of app_id attribute.

Created docs ticket https://jira.mongodb.org/browse/DOCSP-32245
cc @Zuhairahmed

@Zuhairahmed
Copy link
Collaborator

Thanks @maastha and @andreaangiolillo. I added in a simple commit for @zach-carr and team to build off if helpful. Otherwise LGTM

@maastha maastha merged commit 760f4d4 into master Aug 18, 2023
18 checks passed
@maastha maastha deleted the INTMDB-925-trigger-appid-force-new branch August 18, 2023 09:59
Copy link
Contributor

@zach-carr zach-carr left a 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.
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants