Skip to content
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.

Sign up for GitHub

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

chore(metadata): add vpc_service_control_attach_dry_run #905

Merged
merged 3 commits into from
May 2, 2024
+6 −1
Merged

chore(metadata): add vpc_service_control_attach_dry_run #905

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a4079ee
add vpc_service_control_attach_dry_run to the metadata specs so that …
eeaton May 2, 2024
8decb09
Merge branch 'master' into master
apeabody May 2, 2024
54744c2
Merge branch 'master' into master
apeabody May 2, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion metadata.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -334,7 +334,12 @@ spec:
default: ""
required: false
- name: vpc_service_control_attach_enabled
description: Whether the project will be attached to a VPC Service Control Perimeter
description: Whether the project will be attached to a VPC Service Control Perimeter in ENFORCED MODE. vpc_service_control_attach_dry_run should be false for this to be true
type: bool
default: false
required: false
- name: vpc_service_control_attach_dry_run
description: Whether the project will be attached to a VPC Service Control Perimeter in Dry Run Mode. vpc_service_control_attach_enabled should be false for this to be true
type: bool
default: false
required: false
Expand Down