Utility to autogenerate a terraform module
Metadata
Current evaluation
Feature request for a charmcraft terraform command to autogenerate Terraform modules from charm metadata.yaml. Maintainer proposed jinja templates and requested stakeholder feedback in Aug 2024; no response since. Label: Needs information.
Suggested action: close stale
Reason: Maintainer lengau explicitly requested stakeholder feedback on the jinja-template approach on 2024-08-29, and the issue carries the 'Needs information' label. Over 11 months have elapsed with no further response from the reporter or community, exceeding the 6-month threshold. No terraform-related code or commits exist in the repository, confirming the feature was never started.
Impact:
40
Quick Win:
16.0
Staleness:
70
Complexity:
60
Confidence:
72
Support Request:
10
Issue body
### What needs to get done
Terraform modules for charms seem to be quite deterministic and repeatable, for example:
- https://github.com/Gmerold/terraform-juju-cos-lite-k8s/tree/cos-lite-module/modules
- https://github.com/canonical/data-platform-benchmark-env/tree/main/stacks/cos
- https://github.com/canonical/prometheus-k8s-operator/pull/577
- https://github.com/canonical/grafana-agent-k8s-operator/pull/274
If indeed possible, it would be great to enable this for the entire ecosystem with something like
- `charmcraft terraform`
- `tox -e terraform`
And have it evolve organically with each charm.
### Why it needs to get done
A uniform solution for the entire ecosystem, simplifying maintenance overhead for multiple teams.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
16.0
Staleness:
70
Complexity:
60
Confidence:
72
Support Request:
10
|
close stale | Feature request for a charmcraft terraform command to autogenerate Terraform modules from charm metadata.yaml. Maintainer proposed jinja templates and requested stakeholder feedback in Aug 2024; no response since. Label: Needs information. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
80
Complexity:
70
Confidence:
60
Support Request:
10
|
needs triage | Feature request to auto-generate Terraform modules for charms via charmcraft. Currently under discussion with stakeholders evaluating feasibility and template approaches, but remains open with no implementation or decision. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
65
Complexity:
75
Confidence:
70
Support Request:
0
|
keep open | Proposal to add a charmcraft command for auto-generating Terraform modules for charms. Currently under discussion with maintainers exploring jinja templates and stakeholder feedback. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
70
Complexity:
85
Confidence:
70
Support Request:
0
|
keep open | Proposal to add a charmcraft command for auto-generating Terraform modules for charms. Currently awaiting stakeholder feedback on implementation approach and templates. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
75
Complexity:
45
Confidence:
75
Support Request:
5
|
keep open | Proposes a Charmcraft command to auto-generate Terraform modules for charms, reducing manual maintenance. Awaiting stakeholder feedback on feasibility, Jinja template usage, and output structure. Status: Needs information. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.