-
Notifications
You must be signed in to change notification settings - Fork 1
feat(iac-deploy): Create reusable workflow for iac deployments #189
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
Conversation
Previous version no longer supported and calling workflow fails.
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Files
|
Hi and thank you for opening this pull request! 👋🏼 We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted. Details:
Please update the title to follow the conventional commit specification. If you need help, feel free to ask! 😊 |
This can be ignored. The commit scope has been added to the commitlint config file in this PR |
Deploy job was running in PRs when IAC files were unchanged. The if statement has been updated to check if the output is not empty.
5303116
to
46dc366
Compare
apply will also init so plugins will be pulled from cache
Successful plan and apply here: 3ware/aws-network-speciality#89 |
Going to close this PR and raise another for code promotion |
## [4.19.0](v4.18.0...v4.19.0) (2025-04-03) ### Features * **iac-deploy:** Create reusable workflow for iac deployments ([#189](#189)) ([742f0f5](742f0f5))
This PR is included in version 4.19.0 |
The purpose of this workflow is to create a plan comment in the pull request and apply, via merge queue on merge.
Successful applies will trigger code promotion, where the workflow can be called again to apply to a different environment.The environment is provided via an input.