-
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 terraform-deploy
reusable workflow
#59
Conversation
504ae0f
to
1982e2b
Compare
Add terraform-deploy.yaml reusable workflow that deploys the charm using the terraform module and waits for environment steady state. As per juju-wait docs, the environment is considered in a steady state once all hooks have completed running and there are no hooks queued to run, on all units
2529582
to
ecc2675
Compare
@orfeas-k It seems you are using the This way we can avoid having to install an additional snap package. |
terraform-deploy
reusable workflow
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 @orfeas-k , looking good already, just a comment on making sure this works in multi charm repos.
Addterraform-deploy.yaml
reusable workflow that deploys the charm usingthe terraform module and waits for environment steady state. This essentially
transforms https://github.com/canonical/sunbeam-terraform/blob/main/.github/workflows/deploy.yml
into a reusable workflow. As per
juju-wait
help command, the environment isconsidered in a steady state once all hooks have completed running and there
are no hooks queued to run, on all units. This means that the check will succeed
if the charm units go to
idle
.Add
terraform-apply.yaml
reusable workflow that applys the TF module andusing
juju wait-for
, waits for the application to go inactive
or `blocked.