844ebf0dbd
* feat(ssh): enable OS Login for GCP test instances * fix(ssh): force service account impersonation for OS Login * debug: show actual user trying to impersonate SA * fix(glcloud): configure gcloud before running commands * fix(ssh): add VM zone to ssh command * fix(auth): bringing changes from #5614 * fix(auth): impersonation is working as expected now * fix(gcloud): setup the GCP CLI after authenticating (#5606) Previous behavior: `gcloud` commands have been running without an appropiate authentication as the `auth` auction was sucessfully executed, but the actual gcloud CLI being used in further jobs was not using the correct configuration nor credentials Expected behavior: All `gcloud` commands should be properly configured and authenticated. Solution: Add the `google-github-actions/setup-gcloud` action after each `google-github-actions/auth` invocation, and before running any `gcloud` command. Remove the need of an OAuth Access token when not required by following steps * fix(auth): revert to latest version * fix: wrong replace * fix(ci): use a specific debian image for VM containers * fix(ssh): delete generated SSH keys by CI after 30 seconds * debug: remove debug commands * fix(compute): use a lightweight container image * fix(ci): add missing sudo to docker command * Update .github/workflows/deploy-gcp-tests.yml Co-authored-by: Deirdre Connolly <durumcrustulum@gmail.com> * fix(ssh): delete ssh-keys for the specific GHA service account Co-authored-by: Deirdre Connolly <durumcrustulum@gmail.com> |
||
---|---|---|
.. | ||
ISSUE_TEMPLATE | ||
PULL_REQUEST_TEMPLATE | ||
workflows | ||
CODEOWNERS | ||
dependabot.yml | ||
mergify.yml | ||
pull_request_template.md | ||
release-drafter.yml | ||
zbot.yml |