kovagoadi/hunfabric
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[FAST] Rename stage 2-networking-d-separate-envs to 2-netwroking-c-separate-envs (#2328)

Browse Source 
Co-authored-by: Luca Prete <lucaprete@google.com>
This commit is contained in:
Luca Prete
2024-05-31 09:09:31 +03:00
committed by GitHub
parent f8f18734f1
commit eb5754e475
36 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
blueprints/gcve/pc-minimal/README.md
View File

@@ -30,7 +30,7 @@ Based on our GCP best practices, a GCVE private cloud relies on user groups to a
### Network
This blueprints expects the user to provision a VPC upfront, either from one of the FAST networking stages (e.g. [Networking with separated single environment](../../../fast/stages/2-networking-d-separate-envs)) or from an external source.
This blueprints expects the user to provision a VPC upfront, either from one of the FAST networking stages (e.g. [Networking with separated single environment](../../../fast/stages/2-networking-c-separate-envs)) or from an external source.
The blueprint can optionally configure the [VMware Engine Network peering](https://cloud.google.com/vmware-engine/docs/networking/peer-vpc-network) on the peer VPC by granting the following permissions on the project that hosts the VPC:
- vmwareengine.networkPeerings.create
- vmwareengine.networkPeerings.get