add bigquery_dataset_access fine-grained resource #6035
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
* add bigquery_dataset_access fine-grained resource * exclude ansible and inspec * exclude validator * compile * expand and flatten when checking match * add mutex and multiple test Signed-off-by: Modular Magician <magic-modules@google.com>
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks! |
ghost
locked and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes #2686
Includes some changes to nested query func names so they don't conflict with the ones from the parent resource.
Also includes changes to the function that finds matches in nested query: now, instead of comparing the expanded form from the config to the flattened form from the API, it compares the expanded-and-then-flattened form from the config to the flattened form from the API. Without this, we end up comparing a config format (e.g.
user_by_email) to the API format (e.g.userByEmail)Release Note Template for Downstream PRs (will be copied)
Derived from GoogleCloudPlatform/magic-modules#3312