-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Create namespace IAM resource #16175
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
base: main
Are you sure you want to change the base?
Create namespace IAM resource #16175
Conversation
70732f6 to
c1e5353
Compare
|
@SirGitsalot could you take a look at this? |
|
Hello! I am a robot. Tests will require approval from a repository maintainer to run. Googlers: For automatic test runs see go/terraform-auto-test-runs. @melinath, 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. |
melinath
left a comment
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.
hey @rambleraptor!
I've approved the build - note go/terraform-auto-test-runs. @SirGitsalot isn't available at the moment; do they have additional context on this PR?
| DeprecationMessage string `yaml:"deprecation_message,omitempty"` | ||
|
|
||
| // Whether to send the x-goog-user-project header in IAM requests. | ||
| SendsUserProjectHeader bool `yaml:"sends_user_project_header,omitempty"` |
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.
For resources we ended up handling this by making the headers object available for pre_create etc. custom code... but I think it would be fine to use a single flag here for now since we don't have other use cases.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
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.
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_biglake_iceberg_namespace_iam_binding" "primary" {
catalog = # value needed
condition {
description = # value needed
expression = # value needed
title = # value needed
}
members = # value needed
name = # value needed
role = # value needed
}
Resource: resource "google_biglake_iceberg_namespace_iam_member" "primary" {
catalog = # value needed
condition {
description = # value needed
expression = # value needed
title = # value needed
}
member = # value needed
name = # value needed
role = # value needed
}
Resource: resource "google_biglake_iceberg_namespace_iam_policy" "primary" {
catalog = # value needed
name = # value needed
policy_data = # value needed
}
|
Tests analyticsTotal tests: 3306 Click here to see the affected service packages
Action takenFound 7 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
|
🟢 Tests passed during RECORDING mode: 🔴 Tests failed when rerunning REPLAYING mode: Tests failed due to non-determinism or randomness when the VCR replayed the response after the HTTP request was made. Please fix these to complete your PR. If you believe these test failures to be incorrect or unrelated to your change, or if you have any questions, please raise the concern with your reviewer. 🔴 Tests failed during RECORDING mode: 🔴 Errors occurred during RECORDING mode. Please fix them to complete your PR. |
mmv1/templates/terraform/iam/example_config_body/biglake_iceberg_namespace_iam.go.tmpl
Show resolved
Hide resolved
Co-authored-by: Stephen Lewis (Burrows) <stephen.r.burrows@gmail.com>
Co-authored-by: Stephen Lewis (Burrows) <stephen.r.burrows@gmail.com>
Co-authored-by: Stephen Lewis (Burrows) <stephen.r.burrows@gmail.com>
32369c4 to
1ad3c41
Compare
|
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.
Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_biglake_iceberg_namespace_iam_binding" "primary" {
condition {
description = # value needed
expression = # value needed
title = # value needed
}
}
Resource: resource "google_biglake_iceberg_namespace_iam_member" "primary" {
condition {
description = # value needed
expression = # value needed
title = # value needed
}
}
|
Tests analyticsTotal tests: 3305 Click here to see the affected service packages
Action takenFound 5 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
|
🟢 Tests passed during RECORDING mode: 🔴 Tests failed when rerunning REPLAYING mode: Tests failed due to non-determinism or randomness when the VCR replayed the response after the HTTP request was made. Please fix these to complete your PR. If you believe these test failures to be incorrect or unrelated to your change, or if you have any questions, please raise the concern with your reviewer. 🔴 Tests failed during RECORDING mode: 🔴 Errors occurred during RECORDING mode. Please fix them to complete your PR. |
Hello friends! Long time no see!
I've got a bit of a convoluted PR here:
This adds just IAM resources for the BigLake Namespace resource, not the actual BigLake namespace resource. It also adds support for adding the
x-goog-user-projectheader, which is necessary to send over.I've done local testing and this works as expected. We can't use the automated IAM tests to create the actual resource, since we need to use a separate not-yet-published Terraform provider to handle those resources.
(optional - why? The BigLake namespace resource follows the Iceberg REST Catalog spec, which is developed by the Apache Iceberg project. It doesn't follow the Google AIP standard and writing a Terraform resource in Magic Modules would be impossible. The Iceberg project is working on their own Terraform provider and that's the recommended way to manage these Iceberg resources. But, IAM is a Google thing with Google APIs, so we need separate IAM resources).
Release Note Template for Downstream PRs (will be copied)
See Write release notes for guidance.