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

add ForceNew to firewall direction field. #1284

Merged
merged 2 commits into from
Jan 24, 2019
Merged

add ForceNew to firewall direction field. #1284

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
be4687c
add ForceNew to firewall direction field.
nat-henderson Jan 23, 2019
7cd1810
Update tracked submodules -> HEAD on Thu Jan 24 00:20:59 UTC 2019
modular-magician Jan 24, 2019
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
2 changes: 1 addition & 1 deletion build/terraform
Open in desktop
Submodule terraform updated from 6e5bd6 to e53306
2 changes: 1 addition & 1 deletion build/terraform-beta
Open in desktop
Submodule terraform-beta updated from c4faa8 to 87ee5a
5 changes: 5 additions & 0 deletions products/compute/terraform.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -199,6 +199,11 @@ overrides: !ruby/object:Overrides::ResourceOverrides
default_from_api: true
direction: !ruby/object:Overrides::Terraform::PropertyOverride
default_from_api: true
# Because most fields on this resource are `Computed`, it is easy
# for a user to wind up in a broken state if they switch a rule from
# being ingress to egress without examining the diff carefully.
# See terraform issue #2713 for more context.
input: true
name: !ruby/object:Overrides::Terraform::PropertyOverride
validation: !ruby/object:Provider::Terraform::Validation
function: 'validateGCPName'
Expand Down