Skip to content

Rename Config and Plugin to service-specific names#699

Open
ubaskota wants to merge 1 commit into
smithy-lang:developfrom
ubaskota:config_class_update
Open

Rename Config and Plugin to service-specific names#699
ubaskota wants to merge 1 commit into
smithy-lang:developfrom
ubaskota:config_class_update

Conversation

@ubaskota
Copy link
Copy Markdown
Contributor

@ubaskota ubaskota commented May 20, 2026

Issue #, if available:

Description of changes:
Rename generated Config class to service-specific names derived from ServiceTrait sdkId (e.g., BedrockRuntimeConfig). Similarly rename Plugin to <ServiceName>Plugin. Deprecated aliases with DeprecationWarning are generated for backwards compatibility. Generic (Non-AWS SDKs) remain unchanged.

Testing

  • Verified that all tests pass (make test-py and make test-protocols)
  • Verified that “deprecation warning” is emitted when deprecated Config is used
  • Verified that both Config and BedrockRuntimeConfig successfully make requests and receive responses
  • Compared the diffs and verified that there are no changes for non-AWS sdks
  • Compared the diffs and verified that capybara sdk generates BedrockRuntimeConfig/BedrockRuntimePlugin with deprecated aliases as expected

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@ubaskota ubaskota requested a review from a team as a code owner May 20, 2026 03:42
Copy link
Copy Markdown
Contributor

@Alan4506 Alan4506 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM overall. Just curious: why add the changelog entries to aws-sdk-signers, smithy-aws-core, and smithy-aws-event-stream? None of those packages' source actually changes in this PR. Do we have a better way to surface this codegen-level change?

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