Skip to content

[bot] Merge 26.7 to 26.8 - #1483

Merged
github-actions[bot] merged 3 commits into
release26.8-SNAPSHOTfrom
26.8_fb_bot_merge_26.7
Aug 21, 2026
Merged

[bot] Merge 26.7 to 26.8#1483
github-actions[bot] merged 3 commits into
release26.8-SNAPSHOTfrom
26.8_fb_bot_merge_26.7

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Generated automatically.
Merging changes from: 1fa7cf9
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=26.8_fb_bot_merge_26.7

labkey-tchad and others added 3 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
@github-actions
github-actions Bot merged commit e53a532 into release26.8-SNAPSHOT Aug 21, 2026
7 checks passed
@github-actions
github-actions Bot deleted the 26.8_fb_bot_merge_26.7 branch August 21, 2026 20:19
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.

4 participants