Skip to content

[bot] Merge 26.8 to develop - #1487

Open
github-actions[bot] wants to merge 4 commits into
developfrom
fb_bot_merge_26.8
Open

[bot] Merge 26.8 to develop#1487
github-actions[bot] wants to merge 4 commits into
developfrom
fb_bot_merge_26.8

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Generated automatically.
Merging changes from: e53a532
Approve all matching PRs simultaneously.
Approval will trigger automatic merge.
Verify all PRs before approving: https://internal.labkey.com/Scrumtime/Backlog/harvest-gitOpenPullRequests.view?branch=fb_bot_merge_26.8

labkey-tchadand others added 4 commits August 18, 2026 09:26
## Rationale
A customer reported ERROR-level SSM logging on an on-premise server that
never intended to use AWS SSM, because `SsmSecretProvider` treated any
resolvable AWS credentials as a signal to activate. See the linked
premiumModules PR for the full symptom.
This post-processor already computes the right answer —
`hasExplicitConfig` — and returns before touching the AWS SDK
on-premise. It just never told the module. Publishing that decision lets
CloudServices stop inferring intent from whatever credentials happen to
resolve.
No configuration change is needed in cloud deployments: the flag is
published automatically whenever `context.awsParameterStore.prefix` or
`context.awsParameterStore.secretsPrefix` is set, which cloud already
does.
## Related Pull Requests
- LabKey/premiumModules#688
## Changes
- Publish `labkey.aws.ssm.enabled=true` alongside the region and secrets
prefix
Sign up for freeto 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.

3 participants

@labkey-teamcity@labkey-tchad@labkey-jeckels