-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Add support for google_compute_node_group
to TGC
#10635
Add support for google_compute_node_group
to TGC
#10635
Conversation
Hello! I am a robot. Tests will require approval from a repository maintainer to run. @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. |
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.
Since this is a TGC-only change it should use release note type none
and the content of the release note should be empty. Release notes are only used for provider changes.
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.
|
google_compute_node_group
to TGC
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.
TGC converters shouldn't technically need to depend on each other (in most cases) but if there's a separate PR for node template then we should remove that from here for sure, and we could merge them in order if you prefer.
I just did let NodeTemplate here because is a resource dependency for NodeGroup resource. I think we should merge the other PR about NodeTemplate and after merge here. Make sense? |
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.
sounds good, removing from my queue for now - let me know when node template is done & I'll review this at that point.
node template is done, thanks. |
Co-authored-by: Stephen Lewis (Burrows) <stephen.r.burrows@gmail.com>
google_compute_node_group
to TGCgoogle_compute_node_group
to TGC
google_compute_node_group
to TGCgoogle_compute_node_group
to TGC
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.
Please undo the whitespace changes in resource_converters (or do them in a separate PR) - that's going to make this keep running into merge conflicts.
@@ -92,7 +92,9 @@ func ResourceConverters() map[string][]cai.ResourceConverter { | |||
"google_storage_bucket_iam_policy": {resourceConverterStorageBucketIamPolicy()}, | |||
"google_storage_bucket_iam_binding": {resourceConverterStorageBucketIamBinding()}, | |||
"google_storage_bucket_iam_member": {resourceConverterStorageBucketIamMember()}, | |||
"google_cloud_tasks_queue": {cloudtasks.ResourceConverterCloudTasksQueue()}, | |||
"google_compute_node_group": {compute.ResourceConverterComputeNodeGroup()}, | |||
"google_compute_node_template": {compute.ResourceConverterComputeNodeTemplate()}, |
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 is still adding node_template. Please remove this line.
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.
if I remove google_compute_node_template, it will not test node template resource anymore. I can't remove it.
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.
google_compute_node_template support was added in #10602, so it doesn't also need to be added here.
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, done. Thanks
Also please resolve the merge conflicts |
@@ -92,7 +92,9 @@ func ResourceConverters() map[string][]cai.ResourceConverter { | |||
"google_storage_bucket_iam_policy": {resourceConverterStorageBucketIamPolicy()}, | |||
"google_storage_bucket_iam_binding": {resourceConverterStorageBucketIamBinding()}, | |||
"google_storage_bucket_iam_member": {resourceConverterStorageBucketIamMember()}, | |||
"google_cloud_tasks_queue": {cloudtasks.ResourceConverterCloudTasksQueue()}, | |||
"google_compute_node_group": {compute.ResourceConverterComputeNodeGroup()}, | |||
"google_compute_node_template": {compute.ResourceConverterComputeNodeTemplate()}, |
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.
google_compute_node_template support was added in #10602, so it doesn't also need to be added here.
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.
why are there more whitespace changes? Also, in addition to explaining why, please remove them.
There are more whitespace changes because I'm removing those on edit file github. I'm resolving the conflicts and sometimes it comes from main branch and I need to fix all of them. |
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.
Please undo the whitespace changes
done, 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.
|
This PR has been waiting for review for 2 days. 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.
Taking a look at this, it's only exercising a few of the fields on node_group. Could you add a more complete set of fields? As many as possible, ideally. https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_node_group lists the available fields.
@melinath we are using the most simple group of fields that resource can once those are just to test the specific resource. As much more simpler, it'll be better as internal team said. |
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.
the only other resource that could be referenced from a node group is a project, which doesn't seem like an excessive thing to add to this configuration. Please add all fields to the test. Thanks!
added more fields, thanks. |
@melinath could you please review again? |
This PR has been waiting for review for 2 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.
LGTM assuming tests pass
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.
|
@melinath could you please make the merge? |
yep, thanks for the ping! |
…rm#10635) Co-authored-by: Stephen Lewis (Burrows) <stephen.r.burrows@gmail.com>
adding support for compute.googleapis.com/NodeGroup