3.0 - enhanced authentication method support #33
Merged
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
target local placeholder project for auth library
…tor/aws-orchestrator into use-aws-extension-library
pass full auth params object to library
…tor/aws-orchestrator into use-aws-extension-library
…tor/aws-orchestrator into use-aws-extension-library
upgrade to AWS SDK 4
…tor/aws-orchestrator into use-aws-extension-library
provide examples for auth setups with EC2; update changelog;
…chestrator into 3.0-doc-updates
…chestrator into 3.0-doc-updates
bump auth library to latest
…tion; remove logging of sensitive info;
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.
AWS authentication logic has been pulled out to a library for reuse. Most auth fields have been moved to Custom Fields, with the values allowed for Client Machine and Store Path having also changed.
The Store Type AWS-ACM is now moving to AWS-ACM-v3 due to the nature of these changes. Client Machine and Store Path values from previous deployments need to be updated, which is not possible for defined Cert Stores.
Fixes #24
Store Path only allows a single Region, and the entry parameter for Region is removed
Fixes #16
This issue no longer applies, as the field usage has changed and the documentation has changed as a result.