-
Notifications
You must be signed in to change notification settings - Fork 9
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
Create a terraform module for jupyter-ui charm #404
Labels
enhancement
New feature or request
Comments
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-6234.
|
orfeas-k
added a commit
that referenced
this issue
Sep 24, 2024
Create a `terraform/` directory for each of the charms that hosts their individual Terraform modules. It follows the structure proposed in [this spec](https://docs.google.com/document/d/1EG71A2pJ244PQRaGVzGj7Mx2B_bzE4U_OSqx4eeVI1E/edit) and it is based on what was done in canonical/argo-operators#198. Ref #405 Ref #404
orfeas-k
added a commit
that referenced
this issue
Sep 24, 2024
Create a `terraform/` directory for each of the charms that hosts their individual Terraform modules. It follows the structure proposed in [this spec](https://docs.google.com/document/d/1EG71A2pJ244PQRaGVzGj7Mx2B_bzE4U_OSqx4eeVI1E/edit) and it is based on what was done in canonical/argo-operators#198. Ref #405 Ref #404
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context
According to the terraform modules organization spec, this is the first step to provide a terraform solution module. We need to create a terraform module for each charm.
What needs to get done
Create a terraform module for this charm that complies with the spec.
Definition of Done
Charm has a terraform module
The text was updated successfully, but these errors were encountered: