Skip to content

Commit

Permalink
docs: remove pending TODO
Browse files Browse the repository at this point in the history
We can't remove  `actions/checkout` nor set `create_credentials_file` to `false` as next steps won't be able to authenticate to GCP.

We can surely remove `actions/checkout` and leave `create_credentials_file` as `true`, but this will raise a warning on each step, and there's no benefit of doing so.
  • Loading branch information
gustavovalverde committed Jun 29, 2022
1 parent 93414eb commit 99ef632
Showing 1 changed file with 0 additions and 16 deletions.
16 changes: 0 additions & 16 deletions .github/workflows/deploy-gcp-tests.yml
Original file line number Diff line number Diff line change
Expand Up @@ -100,8 +100,6 @@ jobs:
contents: 'read'
id-token: 'write'
steps:
# TODO: can we delete this step and set create_credentials_file to false in Google Cloud?
# Or will that break the slug-action variables we use to find the instance?
- uses: actions/[email protected]
with:
persist-credentials: false
Expand Down Expand Up @@ -169,8 +167,6 @@ jobs:
contents: 'read'
id-token: 'write'
steps:
# TODO: can we delete this step and set create_credentials_file to false in Google Cloud?
# Or will that break the slug-action variables we use to find the instance?
- uses: actions/[email protected]
with:
persist-credentials: false
Expand Down Expand Up @@ -345,8 +341,6 @@ jobs:
contents: 'read'
id-token: 'write'
steps:
# TODO: can we delete this step and set create_credentials_file to false in Google Cloud?
# Or will that break the slug-action variables we use to find the instance?
- uses: actions/[email protected]
with:
persist-credentials: false
Expand Down Expand Up @@ -472,8 +466,6 @@ jobs:
contents: 'read'
id-token: 'write'
steps:
# TODO: can we delete this step and set create_credentials_file to false in Google Cloud?
# Or will that break the slug-action variables we use to find the instance?
- uses: actions/[email protected]
with:
persist-credentials: false
Expand Down Expand Up @@ -533,8 +525,6 @@ jobs:
contents: 'read'
id-token: 'write'
steps:
# TODO: can we delete this step and set create_credentials_file to false in Google Cloud?
# Or will that break the slug-action variables we use to find the instance?
- uses: actions/[email protected]
with:
persist-credentials: false
Expand Down Expand Up @@ -589,8 +579,6 @@ jobs:
contents: 'read'
id-token: 'write'
steps:
# TODO: can we delete this step and set create_credentials_file to false in Google Cloud?
# Or will that break the slug-action variables we use to find the instance?
- uses: actions/[email protected]
with:
persist-credentials: false
Expand Down Expand Up @@ -648,8 +636,6 @@ jobs:
contents: 'read'
id-token: 'write'
steps:
# TODO: can we delete this step and set create_credentials_file to false in Google Cloud?
# Or will that break the slug-action variables we use to find the instance?
- uses: actions/[email protected]
with:
persist-credentials: false
Expand Down Expand Up @@ -796,8 +782,6 @@ jobs:
contents: 'read'
id-token: 'write'
steps:
# TODO: can we delete this step and set create_credentials_file to false in Google Cloud?
# Or will that break the slug-action variables we use to find the instance?
- uses: actions/[email protected]
with:
persist-credentials: false
Expand Down

0 comments on commit 99ef632

Please sign in to comment.