-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Fixed accesscontextmanager spec requirements #7952
Fixed accesscontextmanager spec requirements #7952
Conversation
Hello! I am a robot who works on Magic Modules PRs. I've detected that you're a community contributor. @megan07, a repository maintainer, has been assigned to assist you and help review your changes. ❓ First time contributing? Click here for more detailsYour assigned reviewer will help review your code by:
You can help make sure that review is quick by running local tests and ensuring they're passing in between each push you make to your PR's branch. Also, try to leave a comment with each push you make, as pushes generally don't generate emails. If your reviewer doesn't get back to you within a week after your most recent change, please feel free to leave a comment on the issue asking them to take a look! In the absence of a dedicated review dashboard most maintainers manage their pending reviews through email, and those will sometimes get lost in their inbox. |
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.
this looks good, thank you!
out of curiosity, what was the error the user saw prior to this change?
Basically inability to have empty status blocks, so in bridge perimeters you had to configure one of And it was causing a constant drift between Reference: |
Ok. Were you able to test it out and see this fixed it? I'm just curious because these still exist on the I'm just wondering if that's correct or if we need to remove those? |
We don't need to remove this. Just check how it's translated in the end:
According to https://github.com/hashicorp/terraform-plugin-sdk/blob/main/helper/schema/schema.go#L282 :
|
yup, yup! i agree this change is good, i just wanted to make sure it was solving the ultimate issue. thanks! |
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are. Terraform GA: Diff ( 1 file changed, 3 insertions(+), 3 deletions(-)) |
Tests analyticsTotal tests: Action takenFound 9 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected testsTestAccDataSourceGoogleFirebaseAndroidAppConfig|TestAccDataSourceAlloydbLocations_basic|TestAccComputeFirewallPolicyRule_multipleRules|TestAccWorkstationsWorkstationIamPolicyGenerated|TestAccAlloydbCluster_missingLocation|TestAccApigeeKeystoresAliasesPkcs12_ApigeeKeystoresAliasesPkcs12Example|TestAccAlloydbBackup_missingLocation|TestAccWorkstationsWorkstationConfigIamPolicyGenerated|TestAccApigeeKeystoresAliasesKeyCertFile_apigeeKeystoresAliasesKeyCertFileTestExample |
Tests passed during RECORDING mode: Tests failed during RECORDING mode: Please fix these to complete your PR |
* fixed accesscontextmanager spec requirements fixes hashicorp/terraform-provider-google#14612 * fixed google_access_context_manager_service_perimeter as well
* fixed accesscontextmanager spec requirements fixes hashicorp/terraform-provider-google#14612 * fixed google_access_context_manager_service_perimeter as well
* fixed accesscontextmanager spec requirements fixes hashicorp/terraform-provider-google#14612 * fixed google_access_context_manager_service_perimeter as well
Fixes hashicorp/terraform-provider-google#14612
If this PR is for Terraform, I acknowledge that I have:
make test
andmake lint
in the generated providers to ensure it passes unit and linter tests.Release Note Template for Downstream PRs (will be copied)