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

chore(CI): fix the workflow that comments the docker image on the commit #12693

Merged
merged 1 commit into from
Mar 7, 2024

Conversation

ADD-SP
Copy link
Contributor

@ADD-SP ADD-SP commented Mar 6, 2024

Summary

The ${{ secrets.GHA_COMMENT_TOKEN }} needs to be manually rotated, replacing it by ${{ secrets.GITHUB_TOKEN }}, which is generated by each run of the workflow, so we don't need to rotate tokens anymore.

Checklist

  • [N/A] The Pull Request has tests
  • [N/A] A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
  • [N/A] There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

KAG-4021

@github-actions github-actions bot added the chore Not part of the core functionality of kong, but still needed label Mar 6, 2024
@ADD-SP ADD-SP force-pushed the add_sp/chore-fix-comment-ci branch from d229c80 to 0f3556e Compare March 6, 2024 03:03
@ADD-SP
Copy link
Contributor Author

ADD-SP commented Mar 6, 2024

@ADD-SP ADD-SP force-pushed the add_sp/chore-fix-comment-ci branch from 0f3556e to 24f5cf6 Compare March 6, 2024 03:12
@ADD-SP ADD-SP changed the title chore(CI): replace Bot token by ${{ secrets.GITHUB_TOKEN }} chore(CI): fix the workflow that comments the docker image on the commit Mar 6, 2024
@ADD-SP ADD-SP marked this pull request as ready for review March 6, 2024 03:23
@ADD-SP ADD-SP marked this pull request as draft March 6, 2024 09:42
@ADD-SP ADD-SP force-pushed the add_sp/chore-fix-comment-ci branch from 24f5cf6 to bb340c4 Compare March 6, 2024 09:44
@ADD-SP
Copy link
Contributor Author

ADD-SP commented Mar 6, 2024

@ADD-SP ADD-SP marked this pull request as ready for review March 6, 2024 09:46
@ADD-SP ADD-SP requested a review from AndyZhang0707 March 6, 2024 09:46
@ADD-SP ADD-SP force-pushed the add_sp/chore-fix-comment-ci branch from bb340c4 to d1b02db Compare March 6, 2024 09:47
Replace `${{ secrets.GHA_COMMENT_TOKEN }}` with `${{ secrets.GITHUB_TOKEN }}`.

The `${{ secrets.GHA_COMMENT_TOKEN }}` needs to be manually rotated,
replacing it by `${{ secrets.GITHUB_TOKEN }}`, which is generated by each
run of the workflow, so we don't need to rotate token anymore.
@ADD-SP ADD-SP force-pushed the add_sp/chore-fix-comment-ci branch from d1b02db to 6d9e530 Compare March 6, 2024 09:47
@AndyZhang0707
Copy link
Collaborator

@curiositycasualty could you please give it a look? thanks

@ADD-SP ADD-SP merged commit 109e0b8 into master Mar 7, 2024
13 checks passed
@ADD-SP ADD-SP deleted the add_sp/chore-fix-comment-ci branch March 7, 2024 05:37
@ADD-SP ADD-SP added backport release/2.8.x cherry-pick kong-ee schedule this PR for cherry-picking to kong/kong-ee labels Mar 8, 2024
@team-gateway-bot
Copy link
Collaborator

Git push to origin failed for release/3.5.x with exitcode 1

1 similar comment
@team-gateway-bot
Copy link
Collaborator

Git push to origin failed for release/3.5.x with exitcode 1

@team-gateway-bot
Copy link
Collaborator

Cherry-pick failed for master, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally.

git remote add upstream https://github.com/kong/kong-ee
git fetch upstream master
git worktree add -d .worktree/cherry-pick-12693-to-master-to-upstream upstream/master
cd .worktree/cherry-pick-12693-to-master-to-upstream
git checkout -b cherry-pick-12693-to-master-to-upstream
ancref=$(git merge-base 7c06064e82a6ac73393aa81ffbb62204dbfa75dd 6d9e530ac2e2687d86c4f2fb0a3f08721c1a3899)
git cherry-pick -x $ancref..6d9e530ac2e2687d86c4f2fb0a3f08721c1a3899

@team-gateway-bot
Copy link
Collaborator

Git push to origin failed for release/3.6.x with exitcode 1

1 similar comment
@team-gateway-bot
Copy link
Collaborator

Git push to origin failed for release/3.6.x with exitcode 1

@team-gateway-bot
Copy link
Collaborator

Git push to origin failed for release/3.6.x with exitcode 1

1 similar comment
@team-gateway-bot
Copy link
Collaborator

Git push to origin failed for release/3.6.x with exitcode 1

@team-gateway-bot
Copy link
Collaborator

Git push to origin failed for release/3.3.x with exitcode 1

@team-gateway-bot
Copy link
Collaborator

Git push to origin failed for release/3.4.x with exitcode 1

@team-gateway-bot
Copy link
Collaborator

Git push to origin failed for release/3.5.x with exitcode 1

@team-gateway-bot
Copy link
Collaborator

Git push to origin failed for release/3.6.x with exitcode 1

ADD-SP added a commit that referenced this pull request Mar 8, 2024
…mit (#12693)

Replace `${{ secrets.GHA_COMMENT_TOKEN }}` with `${{ secrets.GITHUB_TOKEN }}`.

The `${{ secrets.GHA_COMMENT_TOKEN }}` needs to be manually rotated,
replacing it by `${{ secrets.GITHUB_TOKEN }}`, which is generated by each
run of the workflow, so we don't need to rotate token anymore.
ADD-SP added a commit that referenced this pull request Mar 8, 2024
…mit (#12693)

Replace `${{ secrets.GHA_COMMENT_TOKEN }}` with `${{ secrets.GITHUB_TOKEN }}`.

The `${{ secrets.GHA_COMMENT_TOKEN }}` needs to be manually rotated,
replacing it by `${{ secrets.GITHUB_TOKEN }}`, which is generated by each
run of the workflow, so we don't need to rotate token anymore.
ADD-SP added a commit that referenced this pull request Mar 8, 2024
…mit (#12693)

Replace `${{ secrets.GHA_COMMENT_TOKEN }}` with `${{ secrets.GITHUB_TOKEN }}`.

The `${{ secrets.GHA_COMMENT_TOKEN }}` needs to be manually rotated,
replacing it by `${{ secrets.GITHUB_TOKEN }}`, which is generated by each
run of the workflow, so we don't need to rotate token anymore.
ADD-SP added a commit that referenced this pull request Mar 8, 2024
…mit (#12693)

Replace `${{ secrets.GHA_COMMENT_TOKEN }}` with `${{ secrets.GITHUB_TOKEN }}`.

The `${{ secrets.GHA_COMMENT_TOKEN }}` needs to be manually rotated,
replacing it by `${{ secrets.GITHUB_TOKEN }}`, which is generated by each
run of the workflow, so we don't need to rotate token anymore.
ADD-SP added a commit that referenced this pull request Mar 8, 2024
…mit (#12693)

Replace `${{ secrets.GHA_COMMENT_TOKEN }}` with `${{ secrets.GITHUB_TOKEN }}`.

The `${{ secrets.GHA_COMMENT_TOKEN }}` needs to be manually rotated,
replacing it by `${{ secrets.GITHUB_TOKEN }}`, which is generated by each
run of the workflow, so we don't need to rotate token anymore.
flrgh pushed a commit that referenced this pull request Mar 12, 2024
…mit (#12693) (#12707)

Replace `${{ secrets.GHA_COMMENT_TOKEN }}` with `${{ secrets.GITHUB_TOKEN }}`.

The `${{ secrets.GHA_COMMENT_TOKEN }}` needs to be manually rotated,
replacing it by `${{ secrets.GITHUB_TOKEN }}`, which is generated by each
run of the workflow, so we don't need to rotate token anymore.
flrgh pushed a commit that referenced this pull request Mar 12, 2024
…mit (#12693) (#12708)

Replace `${{ secrets.GHA_COMMENT_TOKEN }}` with `${{ secrets.GITHUB_TOKEN }}`.

The `${{ secrets.GHA_COMMENT_TOKEN }}` needs to be manually rotated,
replacing it by `${{ secrets.GITHUB_TOKEN }}`, which is generated by each
run of the workflow, so we don't need to rotate token anymore.
flrgh pushed a commit that referenced this pull request Mar 12, 2024
…mit (#12693) (#12709)

Replace `${{ secrets.GHA_COMMENT_TOKEN }}` with `${{ secrets.GITHUB_TOKEN }}`.

The `${{ secrets.GHA_COMMENT_TOKEN }}` needs to be manually rotated,
replacing it by `${{ secrets.GITHUB_TOKEN }}`, which is generated by each
run of the workflow, so we don't need to rotate token anymore.
flrgh pushed a commit that referenced this pull request Mar 12, 2024
…mit (#12693) (#12710)

Replace `${{ secrets.GHA_COMMENT_TOKEN }}` with `${{ secrets.GITHUB_TOKEN }}`.

The `${{ secrets.GHA_COMMENT_TOKEN }}` needs to be manually rotated,
replacing it by `${{ secrets.GITHUB_TOKEN }}`, which is generated by each
run of the workflow, so we don't need to rotate token anymore.
flrgh pushed a commit that referenced this pull request Mar 12, 2024
…mit (#12693) (#12711)

Replace `${{ secrets.GHA_COMMENT_TOKEN }}` with `${{ secrets.GITHUB_TOKEN }}`.

The `${{ secrets.GHA_COMMENT_TOKEN }}` needs to be manually rotated,
replacing it by `${{ secrets.GITHUB_TOKEN }}`, which is generated by each
run of the workflow, so we don't need to rotate token anymore.
AndyZhang0707 pushed a commit that referenced this pull request Jun 21, 2024
…mit (#12693) (#12711)

Replace `${{ secrets.GHA_COMMENT_TOKEN }}` with `${{ secrets.GITHUB_TOKEN }}`.

The `${{ secrets.GHA_COMMENT_TOKEN }}` needs to be manually rotated,
replacing it by `${{ secrets.GITHUB_TOKEN }}`, which is generated by each
run of the workflow, so we don't need to rotate token anymore.
locao pushed a commit that referenced this pull request Jun 22, 2024
Co-authored-by: Zachary Hu <[email protected]>
Co-authored-by: Niklaus Schen <[email protected]>
Co-authored-by: Zhongwei Yao <[email protected]>
Co-authored-by: samugi <[email protected]>
Co-authored-by: Water-Melon <[email protected]>
Co-authored-by: Michael Martin <[email protected]>
Co-authored-by: Kong Team Gateway Bot <[email protected]>
Co-authored-by: Zachary Hu <[email protected]>
Co-authored-by: Qi <[email protected]>
Co-authored-by: Mayo <[email protected]>
Co-authored-by: Wangchong Zhou <[email protected]>
Co-authored-by: Harry <[email protected]>
Co-authored-by: Datong Sun <[email protected]>
Co-authored-by: Vinicius Mignot <[email protected]>
fix directory when stop_kong called (#12713)
fix directory when stop_kong called (#12691)
fix the workflow that comments the docker image on the commit (#12693) (#12711)
fix(ci): replace "cpio" rpm extraction (#13233) (#13263)
fix label-check test (#9717)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherry-pick kong-ee schedule this PR for cherry-picking to kong/kong-ee chore Not part of the core functionality of kong, but still needed size/XS
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants