GoogleCloudPlatform / GoogleCloudPlatform/pubsec-declarative-toolkit
Add single Fortigate VM partner-ready minimal extract for dev - separate from production level hub-env/fortigate package and without need for core-landing-zone
- Dominant language
- Shell
- Stars
- 36
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
# add dry run (still won't be able to test out actual GCP workflow like quota issues for example)
https://kpt.dev/reference/cli/live/apply/
```
--dry-run
```
## 2nd clean deploy kcc-arg-3707 2023
spawn https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/pull/745
script in https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/gh446-hub/solutions/setup.sh
Example/dev level single/quad VPC setup for partner access without having to deploy the core-landing-zone package
An extract of project/hub-env/fortigate
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/tree/main/solutions/project/hub-env/fortigate
see https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/tree/gh654-fortigate-dev-vm
see #258
see #446
see CD #751
## Procedures
- windows rdp into management instance https://cloud.google.com/compute/docs/instances/connecting-to-windows
Contributor guide
Assessment
This issue has not been assessed yet.