More updates 2
This commit is contained in:
@@ -1,11 +1,11 @@
|
||||
# Decentralized firewall management
|
||||
|
||||
This sample shows how a decentralized firewall management can be organized using the [firewall factory](../../factories/net-vpc-firewall-yaml/README.md).
|
||||
This example shows how a decentralized firewall management can be organized using the [firewall factory](../../factories/net-vpc-firewall-yaml/README.md).
|
||||
|
||||
This approach is a good fit when Shared VPCs are used across multiple application/infrastructure teams. A central repository keeps environment/team
|
||||
specific folders with firewall definitions in `yaml` format.
|
||||
|
||||
In the current example multiple teams can define their [VPC Firewall Rules](https://cloud.google.com/vpc/docs/firewalls)
|
||||
In the current blueprint multiple teams can define their [VPC Firewall Rules](https://cloud.google.com/vpc/docs/firewalls)
|
||||
for [dev](./firewall/dev) and [prod](./firewall/prod) environments using team specific subfolders. Rules defined in the
|
||||
[common](./firewall/common) folder are applied to both dev and prod environments.
|
||||
|
||||
@@ -17,7 +17,7 @@ This is the high level diagram:
|
||||

|
||||
|
||||
The rules can be validated either using an automated process or a manual process (or a combination of
|
||||
the two). There is an example of a YAML-based validator using [Yamale](https://github.com/23andMe/Yamale)
|
||||
the two). There is an blueprint of a YAML-based validator using [Yamale](https://github.com/23andMe/Yamale)
|
||||
in the [`validator/`](validator/) subdirectory, which can be integrated as part of a CI/CD pipeline.
|
||||
<!-- BEGIN TFDOC -->
|
||||
|
||||
|
||||
Reference in New Issue
Block a user