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.

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

[tf] Use namespaced output variables for endpoints #214

Open
sed-i opened this issue Oct 16, 2024 · 0 comments
Open

[tf] Use namespaced output variables for endpoints #214

sed-i opened this issue Oct 16, 2024 · 0 comments

Comments

@sed-i
Copy link
Contributor

sed-i commented Oct 16, 2024

We should have "static" entries for all relations. This would also help with code generation.
They should be nested under requires and provides.
We should keep the same structure in the higher level modules (e.g. mimir-ha and then cos-ha).
When we autogenerate this from charm source, the description could be added in as a comment.

Option 1: Mapping from string to string

output "requires" {
  value = {
    mimir_cluster = "mimir-cluster"
  }
}

Option 2: Mapping from string to application

This way, the output variable could be readily used in a juju_integration block.

For example:

output "requires" {
  value = {
    mimir_cluster = application {
      name     = self.app_name
      endpoint = "mimir-cluster"
    }
  }  
}

Not sure if we can use application though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant