fix: ClientFactory not properly inheriting k8s pod identity#36
Open
fix: ClientFactory not properly inheriting k8s pod identity#36
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue #, if available: Issue #35
Description of changes: upgrade AWS Java SDK v2 to latest release to pick up some intermediate change that allows the default authenticator chain to properly inherit credentials from kubernetes pod identity/environment.
Testing done:
sbt packagesbt testsbt package, replaced the .jar file included with mypip installversion of sagemaker-feature-store-pyspark library --> success. (The assume-role works properly now, and the following code for ingesting to online feature store begins executing.)Merge Checklist
General
Tests
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.