-
Notifications
You must be signed in to change notification settings - Fork 4
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
[Feature Requests] Publish a GitHub Action version of the validation #7
Comments
It is easy to run LZA-Validator in action. Here is a example:
Test and verified in my sandbox: BTW, you can use LZA-RepoSync to sync LZA configuration repositories from GitHub, GitLab, Bitbucket to CodeCommit automatically. |
I agree with you that it is easy to run only if we disregard the maintenance of the docker image , however GitHub Actions is a convinient abstraction layer on top of otherwise multistep config, but even just building Docker Images would make a difference , either within GH or at Docker Hub |
Unfortunately, we don't have an image repo for that. You can easily create an action to manage your LZA-Validator image build and publish. |
How about the GitHub registry itself ? |
While the default location for the LZA config is Codepipeline, due the shortfalls for the AWS DevOps tool-chain some LZA customers manage their codebase outside the AWS echo system in some more mature offerings like GH, and as validation should happen also close to the code, GitHub Actions is an obvious choice for this.
While the SSM parameter resolution is a limiting factor, via OIDC should be trivial to address too.
The text was updated successfully, but these errors were encountered: