Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Create a terraform module for knative-serving charm #224

Closed
DnPlas opened this issue Sep 9, 2024 · 2 comments
Closed

Create a terraform module for knative-serving charm #224

DnPlas opened this issue Sep 9, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@DnPlas
Copy link
Contributor

DnPlas commented Sep 9, 2024

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
@DnPlas DnPlas added the enhancement New feature or request label Sep 9, 2024
@syncronize-issues-to-jira Syncronize issues to Jira
Copy link

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-6231.

This message was autogenerated

@orfeas-k orfeas-k mentioned this issue Sep 18, 2024
Merged
orfeas-k added a commit that referenced this issue Sep 24, 2024
@orfeas-k
feat: Add terraform modules for knative-{eventing,operator,serving} (#…
167dea7 
…227)

Create a `terraform/` directory for each of the charms to host 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 #224 
Ref #225 
Ref #226
orfeas-k added a commit that referenced this issue Sep 24, 2024
@orfeas-k
feat: Add terraform modules for knative-{eventing,operator,serving} (#…
f0c5920 
…227)

Create a `terraform/` directory for each of the charms to host 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 #224 
Ref #225 
Ref #226
@orfeas-k orfeas-k mentioned this issue Sep 24, 2024
Merged
@orfeas-k
Copy link
Contributor

Closed by #227 and #228

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@DnPlas @orfeas-k