-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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 app_engine_service_network_settings resource #4810
Add app_engine_service_network_settings resource #4810
Conversation
Hello! I am a robot who works on Magic Modules PRs. I have detected that you are a community contributor, so your PR will be assigned to someone with a commit-bit on this repo for initial review. Thanks for your contribution! A human will be with you soon. @c2thorn, please review this PR or find an appropriate assignee. |
Hey @c2thorn any chance you'll be able to have a look at this soon? I'm not sure what the failing CI checks are |
Hey @matty-rose sorry for the delay and thanks for the ping. The error seems to come from failed Inspec generation, would you mind trying excluding the resource from Inspec like in https://github.com/GoogleCloudPlatform/magic-modules/blob/master/mmv1/products/dataproc/inspec.yaml |
d6e0056
to
89c89dc
Compare
@c2thorn made that change but CI still doesn't seem to be happy |
Hi! I'm the modular magician. Your PR generated some diffs in downstreams - here they are. Diff report:Terraform GA: Diff ( 5 files changed, 563 insertions(+), 2 deletions(-)) |
I have triggered VCR tests based on this PR's diffs. See the results here: "https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=191298" |
I have triggered VCR tests in RECORDING mode for the following tests that failed during VCR: TestAccAppEngineServiceNetworkSettings_appEngineServiceNetworkSettingsExample|TestAccEventarcTrigger_transport You can view the result here: "https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=191331" |
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.
Seems good for the most part, just a couple of questions I want to follow up on. Regarding your first post about testing - one other test we often do is a handwritten one that tests updating every field that is updatable. There aren't a lot of fields here, so it doesn't seem like a big deal. But I would encourage you to at least have tried updating the fields manually if you haven't already.
message: 'message' | ||
properties: | ||
- !ruby/object:Api::Type::String | ||
name: 'service' |
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.
Is this something that is updatable without recreating the resource?
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.
I think technically yes? since the API call the terraform resource makes is only a PATCH - This is another one I took from the SplitTraffic resource since they are very similar, but not really sure on the correct behaviour here
5393c9c
to
74419fb
Compare
Hi! I'm the modular magician. Your PR generated some diffs in downstreams - here they are. Diff report:Terraform GA: Diff ( 6 files changed, 698 insertions(+), 2 deletions(-)) |
I have triggered VCR tests based on this PR's diffs. See the results here: "https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=191701" |
/gcbrun |
I have triggered VCR tests based on this PR's diffs. See the results here: "https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=192076" |
Hi! I'm the modular magician. Your PR generated some diffs in downstreams - here they are. Diff report:Terraform GA: Diff ( 6 files changed, 698 insertions(+), 2 deletions(-)) |
I have triggered VCR tests based on this PR's diffs. See the results here: "https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=192077" |
I have triggered VCR tests in RECORDING mode for the following tests that failed during VCR: TestAccAppEngineServiceNetworkSettings_update You can view the result here: "https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=192083" |
1 similar comment
I have triggered VCR tests in RECORDING mode for the following tests that failed during VCR: TestAccAppEngineServiceNetworkSettings_update You can view the result here: "https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=192083" |
any insights on these test failures @c2thorn? |
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 check was faulty, the tests actually passed! LGTM, I'll get this merged in.
thanks for your assistance @c2thorn ! |
Fixes: hashicorp/terraform-provider-google#7866
Reference: https://cloud.google.com/appengine/docs/admin-api/reference/rest/v1/apps.services#networksettings
I'm not sure whether I need to write more tests for this resource, on top of the generated example one - some other resources seem to only have the generated example test and I couldn't really see a distinction between those had extra tests and those that didn't.
If this PR is for Terraform, I acknowledge that I have:
make test
andmake lint
to ensure it passes unit and linter tests.Release Note Template for Downstream PRs (will be copied)