Skip to content

fix: carry the application_insights sensitive marker back to develop AB#9316 - #42

Merged
kfaessen merged 1 commit into
developfrom
feature/AB9316-restore-appinsights-sensitive-marker
Sep 2, 2026
Merged

kfaessen merged 1 commit into
developfrom
feature/AB9316-restore-appinsights-sensitive-marker

Conversation

@kfaessen

@kfaessen kfaessen commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

The sensitive = true marker on the application_insights.connection_string output was added on main (#40, AB#7844) and never merged back to develop, so develop has been carrying a regression since June.

Any consumer that bumps to a tag cut from develop fails its plan with:

Error: Output refers to sensitive values
  5: output "connection_string" {

Measured on the zsmart_router application_insights data unit against tst. This cherry-picks 7623c12 so a release tag can be cut from develop again.

Terraform/azurerm reject a non-sensitive output that returns the App Insights
connection_string ('Output refers to sensitive values'), which blocks any fresh
apply of a unit using this data module. AB#7844
@kfaessen
kfaessen merged commit a5929dd into develop Sep 2, 2026
1 check passed
@kfaessen
kfaessen deleted the feature/AB9316-restore-appinsights-sensitive-marker branch September 2, 2026 08:45
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