-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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 Beta support for allowedPorts field for Cloud Workstations configurations #11299
Conversation
Hello! I am a robot. Tests will require approval from a repository maintainer to run. @hao-nan-li, 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. |
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.
|
Tests analyticsTotal tests: 36 Click here to see the affected service packages
Action takenFound 11 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
|
@@ -573,6 +580,22 @@ properties: | |||
name: 'disableTcpConnections' | |||
description: | | |||
Disables support for plain TCP connections in the workstation. By default the service supports TCP connections via a websocket relay. Setting this option to true disables that relay, which prevents the usage of services that require plain tcp connections, such as ssh. When enabled, all communication must occur over https or wss. | |||
- !ruby/object:Api::Type::Array |
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.
It's this top-level field required
as well since all inner fields are required
. In that case this field needs to be updated in all existing tests for this 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.
Hi @hao-nan-li, allowed_ports
it self is not required, however if defined, first
and last
are required inside the allowed_ports
argument. Please let me know if i configured this correctly!
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.
|
Tests analyticsTotal tests: 37 Click here to see the affected service packages
Action takenFound 11 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
|
@hao-nan-li This PR has been waiting for review for 3 weekdays. Please take a look! Use the label |
@GoogleCloudPlatform/terraform-team @hao-nan-li This PR has been waiting for review for 1 week. Please take a look! Use the label |
@GoogleCloudPlatform/terraform-team @hao-nan-li This PR has been waiting for review for 2 weeks. Please take a look! Use the label |
Any luck on fixing the tests? |
Hey @hao-nan-li, can you explain why these tests fail? The test i created does not fail correct? Since it takes quite some time to run these tests, it would help if you could share the errors from the VCR tests. (as they all create their own cluster) Thanks! Sorry for missing this. |
I think the added field caused some diff, perhaps this field needs to be added to existing tests. |
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.
|
Tests analyticsTotal tests: 37 Click here to see the affected service packages
Action takenFound 32 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
The field should be optional according to the documentation, which it is right? I thought it might need the
@hao-nan-li what should i do next? I never needed these permissions on organization for testing. |
|
@GoogleCloudPlatform/terraform-team @hao-nan-li This PR has been waiting for review for 3 weeks. Please take a look! Use the label |
@GoogleCloudPlatform/terraform-team @hao-nan-li This PR has been waiting for review for 5 weeks. Please take a look! Use the label |
I am currently on holiday, will pick this up when I am back. |
Hi @daanheikens Tomorrow, the Magic Modules repository is scheduled to undergo a language migration from Ruby to Go. You can view more details about this in our announcement here: hashicorp/terraform-provider-google#19583 (or go/mm-migration-announcement if you are a Googler) This open pull request may become incompatible due to most YAML and .erb files converting to Go-compatible files. Our team (Magic Modules repository maintainers) has tooling to automatically convert changes to the new language, and we can prepare a new commit for this pull request that is compatible with the migration. In order to push the new changes to your pull request, we would need to force push the commit to your fork's branch. Our tooling saves a backup branch before converting, so we could rollback or open a new pull request if needed. We would also work with you and the PR reviewer in the event additional changes are needed. You also have the option to update the pull request yourself after the migration. You can view a preview branch and updated documentation related to the migration changes. We will take no action until we have your explicit permission to push changes to your fork's branch used for this pull request. Let me or your reviewer know if you have any further questions! |
Hi @c2thorn, you can update the branch! All good. Thanks for your message. |
Add update tests Add allowedPorts support for workstation config
Thanks folks, Is this ready to merge now? |
Just added my updates. I think this might fixes the last issues. @hao-nan-li can you run the VCR tests again? |
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.
|
Tests analyticsTotal tests: 37 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: 🟢 No issues found for passed tests after REPLAYING rerun. 🟢 All tests passed! |
@hao-nan-li I think it's fixed, could you review? |
…urations (GoogleCloudPlatform#11299) Co-authored-by: Cameron Thornton <[email protected]>
…urations (GoogleCloudPlatform#11299) Co-authored-by: Cameron Thornton <[email protected]>
…urations (GoogleCloudPlatform#11299) Co-authored-by: Cameron Thornton <[email protected]>
…urations (GoogleCloudPlatform#11299) Co-authored-by: Cameron Thornton <[email protected]>
…urations (GoogleCloudPlatform#11299) Co-authored-by: Cameron Thornton <[email protected]>
…urations (GoogleCloudPlatform#11299) Co-authored-by: Cameron Thornton <[email protected]>
Fixes: hashicorp/terraform-provider-google#18859
Release Note Template for Downstream PRs (will be copied)