Conversation
Co-authored-by: Michael Thamm <mike.thamm@canonical.com> Signed-off-by: Leon <82407168+sed-i@users.noreply.github.com>
|
@sed-i I noticed you have some failing unit tests. Terraform v0.15.0 was recently released and is more strict for variable validation. This will need to be fixed in our monorepo Terraform files, not here. You can merge this PR on 🔴. I will PR the fix for this in another PR. |
YanisaHS
left a comment
YanisaHS
left a comment
There was a problem hiding this comment.
You should say it's with Terraform either in the title or in the intro
I didn't go through it super closely otherwise - but I'm happy to help with them more after the engineering sprint :)
| alertmanager 0.27.0 active 1 alertmanager-k8s latest/edge 158 10.152.183.34 no | ||
| catalogue active 1 catalogue-k8s latest/edge 83 10.152.183.128 no | ||
| grafana 9.5.3 active 1 grafana-k8s latest/edge 146 10.152.183.110 no | ||
| loki 2.9.6 active 1 loki-k8s latest/edge 193 10.152.183.108 no | ||
| prometheus 2.52.0 active 1 prometheus-k8s latest/edge 240 10.152.183.55 no | ||
| traefik 2.11.0 active 1 traefik-k8s latest/edge 236 10.152.183.211 no Serving at 10.211.88.149 |
There was a problem hiding this comment.
This juju status output is heavily outdated. We should update this
| $ juju deploy cos-lite --trust | ||
| ```shell | ||
| terraform init | ||
| terraform apply |
There was a problem hiding this comment.
| terraform apply | |
| terraform apply -var="model=cos-lite" |
|
|
||
| ```bash | ||
| $ terraform init | ||
| $ terraform apply # verify the changes you're applying before accepting! |
There was a problem hiding this comment.
| $ terraform apply -var="model=cos-lite" # verify the changes you're applying before accepting! |
|
|
||
| write_files: | ||
| - source: | ||
| uri: https://github.com/canonical/observability-stack/raw/refs/heads/main/tests/integration/cos/tls_internal/track-dev.tf |
There was a problem hiding this comment.
I see what you are trying to do, but we are not fully ready to move in this direction because it would require a refactor of our itests to get away from Jubilant creating the models. Whereas, in our docs we want to use resource "juju_model" "cos" instead of data ....
See this PR:
4 participants
Issue
Tutorial was outdated.
Solution
Update tutorial, drop irrelevant cloud config script.
Checklist
Context
Testing Instructions
Upgrade Notes