-
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
Modularize workflows by creating reusable GitHub Actions #356
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.
question: are the deleted files referenced somewhere?
no, two were used improperly, as they were two actions made as workflow, so I converted and replaced them, one was unused and had already been converted back into an action |
This PR introduces some new GitHub Actions and modifies existing workflows to use them. The main goal was to reduce code duplication across workflows by extracting common functionality into reusable actions.
Actions created:
azure-login
: For standardized authentication with Azureterraform-setup
: For Terraform version configurationupload-artifact
: For uploading artifacts in pipelinesdownload-artifact
: For downloading artifacts in pipelinesnode-setup
: For configuring Node.js environmentget-all-modules
andget-modified-modules
: For managing Terraform modulesslack-notification
: For sending on slack channel a notificationOther changes:
get-terraform-version
action with new terraform version inputcdn-code-deploy
to maintein conventionget_terraform_version.yaml
,get_all_modules.yaml
andget_modified_modules.yaml
workflow to use new actionsBenefits:
sha
)Resolves: CES-737