-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
google_compute_public_advertised_prefix adding in output only shared_secret #11146
Conversation
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
Hello! I am a robot. Tests will require approval from a repository maintainer to run. @roaks3, a repository maintainer, has been assigned to review your changes. If you have not received review feedback within 2 business days, please leave a comment on this PR asking them to take a look. You can help make sure that review is quick by doing a self-review and by running impacted tests locally. |
Tests analyticsTotal tests: 966 Click here to see the affected service packages
View the build log |
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.
LGTM, but wanted to double check, were you able to verify that the field was returned as expected during local testing?
I wasn't able to deploy it out unfortunately, I tried to test with the example but I dont have the requires that the docs outline in place https://cloud.google.com/vpc/docs/create-pap#create-pap I would need to create a ROA request I believe as well. I figured since it was an output only field it was ok to just add it in. |
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.
Ok, sounds good. It does seem safe to change, but perhaps we can confirm with the user that this fixes the issue for them.
Also, could you check the CLA issue? I'm not sure if you need to make the commit with another account. |
I'll check with them and see if I can get the, to test
Also fixed the CLA issue should be good now I have the app installed |
/gcbrun |
Tests analyticsTotal tests: 966 Click here to see the affected service packages
View the build log |
@roaks3 This PR has been waiting for review for 3 weekdays. Please take a look! Use the label |
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.
Just waiting on CLA fix to merge
Tests analyticsTotal tests: 971 Click here to see the affected service packages
View the build log |
…secret (GoogleCloudPlatform#11146) Co-authored-by: NA2047 <NA2047@users.noreply.github.com>
…secret (GoogleCloudPlatform#11146) Co-authored-by: NA2047 <NA2047@users.noreply.github.com>
…secret (GoogleCloudPlatform#11146) Co-authored-by: NA2047 <NA2047@users.noreply.github.com>
Adding in shared_secret
fixes hashicorp/terraform-provider-google#18171
Please self-review your PR against the review checklist before creating it: https://googlecloudplatform.github.io/magic-modules/contribute/review-pr/
Completing the checklist will help speed up the review process, and we appreciate you spending time on them before sending
your code to be reviewed.
If your PR is still work in progress, please create it in draft mode
-->
Release Note Template for Downstream PRs (will be copied)