Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Configured endpoint resolution (aka service-specific endpoint configuration) #1861

Merged
merged 23 commits into from
Jan 10, 2025

Conversation

sichanyoo
Copy link
Contributor

@sichanyoo sichanyoo commented Jan 8, 2025

Companion PR: smithy-lang/smithy-swift#895

Issue #

152

Description of changes

  • Adds endpoint config resolution feature that allows global / service-specific endpoint configuration via environment variables and shared config file.

New/existing dependencies impact assessment, if applicable

Conventional Commits

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@sichanyoo sichanyoo changed the title feat: Endpoint config resolution (aka service-specific endpoint configuration) feat: Configured endpoint resolution (aka service-specific endpoint configuration) Jan 9, 2025
Sichan Yoo added 4 commits January 10, 2025 09:15
…ervices section referenced by resolved profile doesn't exist, and add check for empty values for reoslved endpoint (empty values = proceed to next possible source). Implementation is 100% matching to SEP now.
@sichanyoo sichanyoo merged commit 2b8b613 into main Jan 10, 2025
25 checks passed
@sichanyoo sichanyoo deleted the feat/endpoint-config-resolution branch January 10, 2025 18:10
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