Skip to content

Track the TF spec migration for product modules #201

@MichaelThamm

Description

@MichaelThamm
  • Update the docs for TF usage and explanations: Tutorials, HowTo

For each charm repo (on main), we need to:

  1. split the endpoints into requires/provides
  2. Tagging for TF modules in charm repos observability#427
  3. add a providers.tf and terraform.tf file, where the terraform.tf file basically becomes what was our providers.tf and the providers.tf becomes the implementation (with config) for the Juju provider.
  4. Add a description to the constraints Terraform input variables so people know that this applies to all workload containers.
    5. Make sure this is clear in the TF provider docs for that variable since the stack blindly points at it per charm variables.
    6. k8s resource patch is losing the fight with juju observability-libs#128

For the stack we need to:

  1. add variables for inputs: juju_controller, proxy, logging-config
  2. add outputs: models, metadata
  • optional: offers, credentials

Monolithics:

Microservices:

Mesh charms:

Testing

  1. Make sure to test the changes by running just terraform-validate in the observability-stack repo.
  2. Update all READMEs for updates to the module sources, variable defaults, and outputs.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions