The GCP PubSec Declarative Toolkit is a collection of declarative solutions to help you on your Journey to Google Cloud. Solutions are designed using Config Connector and deployed using Config Controller.
copy/update the host-project public-dns.yaml resources into it, however they will be placed in comment for easier transition. DNS resources for the client will be deployed in this project instead of the host project. The same zone can't exist twice, and a zone can't be deleted if it contains recordset(s).
add a notice in the host-project public-dns.yaml that it will be transitioned.
VPC host project
add new nonp and pbmm host projects, keeping only appropriate subnets.
label resources under client-folder/standard/applications-infrastructure/host-project as "legacy" for post-transition cleanup.
Firewall policies rules:
label "standard" and "applications-infrastructure" folder firewall-policy as "legacy" for post-transition cleanup.
replicate the client-folder/standard/applications-infrastructure/firewall-policy resources under the pbmm AND nonp folders (adjusting resource names and references accordingly).
in preparation for feature #883
NOTICE: setters have been modified
client-landing-zone
package:public-dns.yaml
resources into it, however they will be placed in comment for easier transition. DNS resources for the client will be deployed in this project instead of the host project. The same zone can't exist twice, and a zone can't be deleted if it contains recordset(s).nonp
andpbmm
host projects, keeping only appropriate subnets.client-folder/standard/applications-infrastructure/host-project
as "legacy" for post-transition cleanup.client-folder/standard/applications-infrastructure/firewall-policy
resources under the pbmm AND nonp folders (adjusting resource names and references accordingly).