Skip to content

Refactor and move config resolution codegen logic from generic layer to AWS layer#659

Open
ubaskota wants to merge 2 commits intosmithy-lang:config_resolution_mainfrom
ubaskota:config_codegen_update
Open

Refactor and move config resolution codegen logic from generic layer to AWS layer#659
ubaskota wants to merge 2 commits intosmithy-lang:config_resolution_mainfrom
ubaskota:config_codegen_update

Conversation

@ubaskota
Copy link

Issue #, if available:

Description of changes:
Moved AWS-specific config resolution codegen (descriptors, validators, custom resolvers, default values) out of the generic ConfigProperty and ConfigGenerator into the AWS codegen layer. Introduced AwsConfigResolutionIntegration as a CodeInterceptor that transforms the generated Config class to inject descriptor support, resolver initialization, and source tracking. Each integration now owns its own property metadata (e.g., SDK_UA_APP_ID_METADATA lives in AwsUserAgentIntegration). The generic codegen layer (codegen/core/) has zero diff from develop.

Testing

  • Verified that the config file is generated with descriptor, resolver and validators.
  • Verified that the config file for the generic sdk is unchanged.
  • Ran tests using the the generated config file and verified that all tests pass.

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 March 16, 2026 22:49
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