-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: add eks cluster gha #112
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the review and the highlights @Langleu ;) . After some consideration, I've opted for a solution that we will/should reuse in our other repositories if it works for you:
Overall, these solutions automate processes and can be reused across repositories. Additionally, since some GHA documentation is now generated automatically, we face a similar issue to https://github.com/orgs/camunda/projects/87?pane=issue&itemId=75474510. I plan to extend this issue to include a bot that will, for each Renovate PR, perform a pre-commit run and commit any necessary modifications. This should address all our documentation update needs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't recheck everything as a lot has changed. Just had a brief look.
I didn't know we had a problem with yaml formatting ^^, it's definitely a sight to get used to concerning the new spacing.
Lint + Test failing atm.
Hello @Langleu, thanks, indeed some formatting was broken Once camunda/infraex-common-config#54 is merged, I'll update the reference in this repo Currently, 2 TODOs have been added:
I'm fine merging this PR and updating the references in once it's merged |
implements https://github.com/camunda/team-infrastructure-experience/issues/307
it also add a renovate tag for aurora and pin some actions