ae86678034
* fix(cd): allow deploying instance templates without disk errors Motivation: PR #5670 failed in `main` as it was tested with `gcloud compute instances create-with-container` and even the manual deployment uses `instances`, and it works. But the one that failed uses `gcloud compute instance-templates create-with-container` using `instance-template` and it's complaining with: `When attaching or creating a disk that is also being mounted to a container, must specify the disk name` Based on the documentation, the name is optional when using `create-with-container`, for both `instances` and `instance-templates` Source: https://cloud.google.com/sdk/gcloud/reference/compute/instance-templates/create-with-container#--container-mount-disk Solution: Revert this specific job as how it was, and do not scale the instances above 1, as this would cause the following error: `Instance template specifies a disk with a custom name. This will cause instance group not to scale beyond 1 instance per zone.` * chore: reduce diff |
||
|---|---|---|
| .. | ||
| ISSUE_TEMPLATE | ||
| PULL_REQUEST_TEMPLATE | ||
| workflows | ||
| CODEOWNERS | ||
| dependabot.yml | ||
| mergify.yml | ||
| pull_request_template.md | ||
| release-drafter.yml | ||
| zbot.yml | ||