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: Correctly handle GCP updates of mongodbatlas_network_peering #2306

Merged
merged 5 commits into from
May 28, 2024

Conversation

oarbusi
Copy link
Collaborator

@oarbusi oarbusi commented May 27, 2024

Description

Correctly handle GCP updates of mongodbatlas_network_peering

Link to any related issue(s): CLOUDP-250605

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. A migration guide must be created or updated if the new feature will go in a major version.
  • Breaking change (fix or feature that would cause existing functionality to not work as expected). Please, add the "breaking change" label to the PR. A migration guide must be created or updated.
  • This change requires a documentation update
  • Documentation fix/enhancement

Required Checklist:

  • I have signed the MongoDB CLA
  • I have read the contributing guides
  • I have checked that this change does not generate any credentials and that they are NOT accidentally logged anywhere.
  • 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
  • If changes include deprecations or removals, I defined an isolated PR with a relevant title as it will be used in the auto-generated changelog.
  • If changes include removal or addition of 3rd party GitHub actions, I updated our internal document. Reach out to the APIx Integration slack channel to get access to the internal document.

Further comments

@github-actions github-actions bot added the bug label May 27, 2024
@oarbusi oarbusi marked this pull request as ready for review May 27, 2024 07:47
@oarbusi oarbusi requested review from a team as code owners May 27, 2024 07:47
Copy link
Contributor

APIx bot: a message has been sent to Docs Slack channel

@@ -142,6 +142,52 @@ func TestAccNetworkRSNetworkPeering_basicGCP(t *testing.T) {
})
}

func TestAccNetworkRSNetworkPeering_updateBasicGCP(t *testing.T) {
acc.SkipTestForCI(t) // needs GCP configuration
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it doable to enable in CI or it's very complicated?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have run the tests but I have done it using my GCP account. If we are able to have a generic account for the team we could do it, but I didn't want to use my account credentials to run the tests in CI.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that's for sure. maybe we can create a triage ticket to have test credentials in GCP

Copy link
Collaborator Author

@oarbusi oarbusi May 27, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will create the ticket! Thanks
edit: created CLOUDP-250829

Copy link
Member

@AgustinBettati AgustinBettati left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -142,6 +142,52 @@ func TestAccNetworkRSNetworkPeering_basicGCP(t *testing.T) {
})
}

func TestAccNetworkRSNetworkPeering_updateBasicGCP(t *testing.T) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just to confirm, with the previous implementation this test was failing in the patch request right?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes exactly. It was failing because update is not possible if the Status is Available

Copy link
Collaborator

@EspenAlbert EspenAlbert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

Copy link
Contributor

@kanchana-mongodb kanchana-mongodb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM / 1 nit

.changelog/2306.txt Outdated Show resolved Hide resolved
Co-authored-by: kanchana-mongodb <[email protected]>
@oarbusi oarbusi merged commit f81f690 into master May 28, 2024
32 checks passed
@oarbusi oarbusi deleted the CLOUDP-250605 branch May 28, 2024 13:37
svc-apix-Bot added a commit that referenced this pull request May 28, 2024
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.

5 participants