Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove Prod-Pipes PAT #117

Merged
merged 2 commits into from
Nov 6, 2023
Merged

Remove Prod-Pipes PAT #117

merged 2 commits into from
Nov 6, 2023

Conversation

MattWellie
Copy link
Contributor

@MattWellie MattWellie commented Nov 6, 2023

Repo is no longer private, and this expired token is crashing the deploy workflow
Also bumps the gcloud setup workflow which is available at V1
https://github.com/marketplace/actions/set-up-gcloud-cloud-sdk-environment

Repo is no longer private, and this expired token is crashing the deploy workflow
@MattWellie MattWellie requested a review from jmarshall November 6, 2023 03:25
@MattWellie
Copy link
Contributor Author

useful thread actions/checkout#664

Copy link
Contributor

@jmarshall jmarshall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree that this token line needs to be deactivated and the setup-gcloud@v1 change is good. A comment for your consideration about how to keep the token documentation for the future…

@@ -87,8 +87,6 @@ jobs:
ref: "main"
path: "production-pipelines"
submodules: recursive
# Comment this line out to revert to using the default $GITHUB_TOKEN.
token: ${{ secrets.PRODUCTION_PIPELINES_RAW_REPO_TOKEN }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is the one I was expecting to stop working when this token expired. The others can fall back to unauthenticated access to now-public repositories, but not this one that's explicitly setting an action's token parameter.

So that this remains a hint for next time we have to make that repo private (hopefully never happens, but it's hard to make predictions about the future), I'd rather this was just commented out and the comment I guess updated to something like Uncomment this line and set up a PAT if production-pipelines needs to be taken private.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fair comment, I'll do that instead!

@MattWellie MattWellie merged commit be4c8e7 into main Nov 6, 2023
1 check passed
@MattWellie MattWellie deleted the Remove-GitHub-PAT branch November 6, 2023 04:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants