Fixed e2e tests for alloydb module #2321
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wiktorn
force-pushed
the
bruzz-alloydb-e2e-fix
branch
from
bfb9b77 to
efd7076
Compare
wiktorn
force-pushed
the
bruzz-alloydb-e2e-fix
branch
from
efd7076 to
53473c1
Compare
wiktorn
approved these changes
May 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed issue with AlloyDB e2e tests. I had to add ignore_changes due to a bug in the API (not yet managed in the provider) causing an attribute not being set and plan never aligned with infrastructure state.
I applicable, I acknowledge that I have:
terraform fmton all modified filestools/tfdoc.py