Repository navigation
feat: expose Application Insights connection_string output AB#7636 - #38
Merged
kfaessen merged 1 commit intoJun 11, 2026
Merged
Conversation
Adds a connection_string output to the application_insights data module so consumers can wire APPLICATIONINSIGHTS_CONNECTION_STRING instead of the deprecated APPINSIGHTS_INSTRUMENTATIONKEY.
nbroers-hanab
approved these changes
Jun 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Wat
Voegt een
connection_stringoutput toe aan hetapplication_insightsdata-module.Waarom
Consumers (o.a. de nieuwe service-tickets incoming-handler Function App, AB#7636) kunnen hiermee
APPLICATIONINSIGHTS_CONNECTION_STRINGbedraden i.p.v. de deprecatedAPPINSIGHTS_INSTRUMENTATIONKEY. De connection string is toekomstbestendig (regionale ingestion) en wordt door de Functions worker-SDK automatisch opgepikt.Impact
Pure additieve wijziging — net-diff t.o.v. v4.2.5 is enkel deze output. Geen breaking changes voor bestaande consumers. Na merge een
v4.2.6tag releasen; de incoming-handler env.hcl's verwijzen daar al naar.terraform validate✓