-
Notifications
You must be signed in to change notification settings - Fork 11
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 mlflow-server charm #266
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-6242.
|
DnPlas
added a commit
that referenced
this issue
Sep 18, 2024
This commit adds the terraform/ directory to the root of the repository to host the Terraform module of this charm. This follows the standard set in CC006. For more information please also refer to canonical/argo-operators/pull/198. Fixes #266
DnPlas
added a commit
that referenced
this issue
Sep 18, 2024
This commit adds the terraform/ directory to the root of the repository to host the Terraform module of this charm. This follows the standard set in CC006. For more information please also refer to canonical/argo-operators/pull/198. Fixes #266
DnPlas
added a commit
that referenced
this issue
Sep 20, 2024
* feat: add Terraform module for mlflow-server This commit adds the terraform/ directory to the root of the repository to host the Terraform module of this charm. This follows the standard set in CC006. For more information please also refer to canonical/argo-operators/pull/198. Fixes #266
DnPlas
added a commit
that referenced
this issue
Sep 24, 2024
Since the default for deploying the charm is now set to latest/edge in the re-usable workflow, this is not required anymore. Part of #266
DnPlas
added a commit
that referenced
this issue
Sep 24, 2024
The latest standard for the terraform/ README.md is that the compatibility note can be obviated since the module at the branch is compatible with the charm in the same branch. Part of #266
DnPlas
added a commit
that referenced
this issue
Sep 24, 2024
* ci: remove the channel from terraform checks Since the default for deploying the charm is now set to latest/edge in the re-usable workflow, this is not required anymore. Part of #266 * docs: remove compatibility note The latest standard for the terraform/ README.md is that the compatibility note can be obviated since the module at the branch is compatible with the charm in the same branch. Part of #266
DnPlas
added a commit
that referenced
this issue
Sep 24, 2024
* feat: add Terraform module for mlflow-server This commit adds the terraform/ directory to the root of the repository to host the Terraform module of this charm. This follows the standard set in CC006. For more information please also refer to canonical/argo-operators/pull/198. Fixes #266
DnPlas
added a commit
that referenced
this issue
Sep 24, 2024
* ci: remove the channel from terraform checks Since the default for deploying the charm is now set to latest/edge in the re-usable workflow, this is not required anymore. Part of #266 * docs: remove compatibility note The latest standard for the terraform/ README.md is that the compatibility note can be obviated since the module at the branch is compatible with the charm in the same branch. Part of #266
DnPlas
added a commit
that referenced
this issue
Sep 25, 2024
* feat: add Terraform module for mlflow-server This commit adds the terraform/ directory to the root of the repository to host the Terraform module of this charm. This follows the standard set in CC006. For more information please also refer to canonical/argo-operators/pull/198. Fixes #266
DnPlas
added a commit
that referenced
this issue
Sep 25, 2024
* ci: remove the channel from terraform checks Since the default for deploying the charm is now set to latest/edge in the re-usable workflow, this is not required anymore. Part of #266 * docs: remove compatibility note The latest standard for the terraform/ README.md is that the compatibility note can be obviated since the module at the branch is compatible with the charm in the same branch. Part of #266
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: