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

Warden promotion workflow #178

Merged
merged 6 commits into from
Jan 23, 2024

Conversation

kwiatekus
Copy link
Collaborator

Description

Changes proposed in this pull request:

  • Allow rendering warden manfiest with desired skr config version and pushing to SKR release channel

@kyma-bot kyma-bot added cla: yes Indicates the PR's author has signed the CLA. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 19, 2024
@kwiatekus kwiatekus added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 19, 2024
@kwiatekus kwiatekus self-assigned this Jan 19, 2024
@kyma-bot kyma-bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jan 22, 2024
@kwiatekus kwiatekus removed their assignment Jan 22, 2024
@kwiatekus kwiatekus removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 22, 2024
@pPrecel pPrecel self-assigned this Jan 22, 2024
Copy link
Collaborator

@pPrecel pPrecel left a comment

Choose a reason for hiding this comment

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

Looks ok. Only a few suggestions and one critical change request related with the checkout functionality


upgrade-images:
name: Bump warden images references
needs: verify-head-status
Copy link
Collaborator

Choose a reason for hiding this comment

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

Needs a job that does not exist. Please remove it

run: |
git config --global user.email "${BOT_EMAIL}"
git config --global user.name "${BOT_USERNAME}"
git clone "https://${BOT_USERNAME}:${GH_ENTERPRISE_TOKEN}@github.tools.sap/${BOT_USERNAME}/module-manifests.git"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is the internal Github URL, not sensitive data enough to hide it in secret/env?

- name: Checkout code
uses: actions/checkout@v4
with:
fetch-depth: 0
Copy link
Collaborator

Choose a reason for hiding this comment

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

The actions/checkout@v4 action by default checkouts to the SHA in the action context that triggered the workflow. In this case, we need to checkout to new SHA created by push in the first job (upgrade-images). I would suggest to add ref: ${{ github.ref_name }} arg.

@kyma-bot kyma-bot added the lgtm Looks good to me! label Jan 23, 2024
@kyma-bot kyma-bot merged commit e77723e into kyma-project:main Jan 23, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes Indicates the PR's author has signed the CLA. lgtm Looks good to me! size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants