Skip to content

fix(ske-observability): remove read-only continue from alert route#9

Merged
h3adex merged 1 commit into
stackitcloud:mainfrom
dieg666:fix/observability-route-continue-readonly
Jun 2, 2026
Merged

fix(ske-observability): remove read-only continue from alert route#9
h3adex merged 1 commit into
stackitcloud:mainfrom
dieg666:fix/observability-route-continue-readonly

Conversation

@dieg666
Copy link
Copy Markdown

@dieg666 dieg666 commented Jun 2, 2026

route.continue is a read-only (computed) attribute of stackit_observability_instance; setting it broke terraform validate with Invalid Configuration for Read-Only Attribute. Affects both observability examples.

Description

route.continue is a Read-Only (computed) attribute of stackit_observability_instance,
but both observability examples set continue = true in local.alert_config.route, so
they fail terraform validate:

Error: Invalid Configuration for Read-Only Attribute
  with stackit_observability_instance.example
  Cannot set value for this attribute as the provider has marked it as read-only.

Removes the offending line from:

  • examples/ske-observability-log-alerts/main.tf
  • examples/ske-observability-alerting-kube-state-metrics/main.tf

continue is only meaningful on child route.routes[], not the root route, so dropping
it is also semantically correct.

Ref: provider docs for stackit_observability_instance
(route nested schema continue listed under Read-Only).

Checklist

  • The CI pipeline passed successfully.

route.continue is a read-only (computed) attribute of stackit_observability_instance; setting it broke terraform validate with Invalid Configuration for Read-Only Attribute. Affects both observability examples.
@h3adex
Copy link
Copy Markdown
Collaborator

h3adex commented Jun 2, 2026

Ty!

@h3adex h3adex merged commit 9a04e22 into stackitcloud:main Jun 2, 2026
3 checks passed
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

Successfully merging this pull request may close these issues.

2 participants