Add google_site_verification_owner resource #8287
Merged
Conversation
This file contains hidden or 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
Co-authored-by: Thomas Rodgers <[email protected]> [upstream:97023007d8f027cfba8fd765bcadffcea0dc2b3b] Signed-off-by: Modular Magician <[email protected]>
modular-magician
deleted the
downstream-pr-97023007d8f027cfba8fd765bcadffcea0dc2b3b
branch
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.
This is the third and final (hopefully) PR implementing issue 5698. The first two were #10999 and #11624.
google_site_verification_owneris a fine grained resource on theownersfield ofgoogle_site_verification_web_resource. That field is a little funky: it's automatically populated with every user that has verified ownership and every user that verified owners have optionally added. What makes it particularly funky is that multiple users can independently verify ownership, for example:[email protected]verifieswww.example.com, theownersfield will contain["[email protected]"][email protected]verifieswww.example.com, theownersfield now contains["[email protected]", "[email protected]"][email protected]as an owner, theownersfield now contains["[email protected]", "[email protected]", "[email protected]"]Verified owners aren't explicitly configured either; they're implicitly added based on the authenticated identity of the user requesting verification.
There's more info about the resource in the included markdown doc.
Release Note Template for Downstream PRs (will be copied)
Derived from GoogleCloudPlatform/magic-modules#11716