← Back to issue list

Utility to autogenerate a terraform module

View original Github issue

Metadata

Project
charmcraft
Number
#1518
Type
issue
State
open
Author
sed-i
Labels
Status: Needs information
Created
Updated
Closed
—

Current evaluation

Feature request to add `charmcraft terraform` to autogenerate Terraform modules from charm metadata. Valid and maintainer-endorsed (gatici, Gmerold, lengau), but no implementation exists; lengau asked about jinja templating and stakeholder ownership, awaiting reply.

Suggested action: keep open

Reason: Maintainers engaged positively — lengau proposed a concrete direction ("Would it be reasonable to use jinja templates to generate the Terraform modules? ... with the command being marked as experimental") and gatici noted Telco already hand-writes such modules — but no terraform code exists in the tree (grep for 'terraform' returns zero matches; git log -S 'terraform' finds no commits), so nothing to close as resolved. The 'Status: Needs information' label reflects the unanswered design question (380 days of silence from the reporter), not obsolescence; this is a broadly desired ecosystem capability that remains valid and triaged.

Evaluated by: mr-cal-bot

Impact: 55 Quick Win: 7 Complexity: 68 Confidence: 74 Actionability: 40

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
stealth/space-bunny-alpha
Impact: 55
Quick Win: 7
Complexity: 68
Confidence: 74
Actionability: 40
keep open Feature request to add `charmcraft terraform` to autogenerate Terraform modules from charm metadata. Valid and maintainer-endorsed (gatici, Gmerold, lengau), but no implementation exists; lengau asked about jinja templating and stakeholder ownership, awaiting reply.
stealth/space-bunny-alpha
Impact: 55
Quick Win: 7
Complexity: 70
Confidence: 78
Actionability: 40
keep open Feature request for a `charmcraft terraform` command to auto-generate Terraform modules from charm metadata. Valid and maintainer-acknowledged (Jira CRAFT-2492), but no implementation; awaiting design/stakeholder feedback on templates.
~deepseek/deepseek-pro-latest
Impact: 45
Quick Win: 7
Complexity: 60
Confidence: 65
Actionability: 40
keep open Feature request for a `charmcraft terraform` command to auto-generate Terraform modules from charm metadata. Maintainer-acknowledged (Jira CRAFT-2492) but awaiting design/stakeholder feedback; no implementation yet.
qwen/qwen3.6-35b-a3b
Impact: 55
Quick Win: 7
Complexity: 70
Confidence: 65
Actionability: 45
keep open Feature request to add a charmcraft terraform command that auto-generates Terraform modules for charms. Has community interest and stakeholder feedback but no implementation yet.
qwen/qwen3.8-27b
Impact: 40
Quick Win: 16
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.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.