Skip to content

chore: bump SDK to v6.0.0 + migrate Config access through GetConfig#140

Closed
kaidaguerre wants to merge 2 commits into
mainfrom
v6-sdk-migration
Closed

chore: bump SDK to v6.0.0 + migrate Config access through GetConfig#140
kaidaguerre wants to merge 2 commits into
mainfrom
v6-sdk-migration

Conversation

@kaidaguerre
Copy link
Copy Markdown

Migrates connection.Config direct reads to connection.GetConfig() per steampipe-plugin-sdk v6.0.0 (see steampipe-plugin-sdk#938). Slack-side rollout of the same fix that landed for AWS in steampipe-plugin-aws#2756. Build, vet, test, and go test -race all green.

Migrates connection.Config direct reads to connection.GetConfig() per
steampipe-plugin-sdk v6.0.0. The SDK now guards Connection.Config
under a per-connection sync.RWMutex (see steampipe-plugin-sdk#938) -
direct field reads from worker goroutines would race with the SDK's
in-place mutation during credential rotation.

Bumps go directive to 1.26 (required by SDK v6).
@kaidaguerre
Copy link
Copy Markdown
Author

Closing — this PR does not fix a customer-visible bug.

Slack auth uses a single static OAuth token field with no rotation machinery. Pipes does not push rotated credentials into the slack plugin's connection config, so the v6 SDK race fix doesn't address any failure mode for this plugin.

The CHANGELOG entry here was already _Dependencies_-only (correct framing for what changes), but the SDK bump alone delivers no customer-visible behavior change. Closing as part of a batch review that found only the aws plugin (already shipped in turbot/steampipe-plugin-aws#2756) has the actual rotation race the v6 SDK fix targets.

If a pure dependency-hygiene bump becomes desirable later as routine maintenance, a new PR would be the right shape.

@kaidaguerre kaidaguerre deleted the v6-sdk-migration branch May 20, 2026 16:29
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.

1 participant