-
Notifications
You must be signed in to change notification settings - Fork 467
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
[#367] Enhanced multi-lang AWSCredentialsProvider=...
decoder and c…
#1184
Conversation
With this commit, KCL multi-lang customers should have greater control over the STS provider. For example, a
... to:
... which satisfies the external id request (issue #367). Additionally, STS-via-VPC should be accessible via:
|
5389a0f
to
c0be0cb
Compare
…r and construction. + added support for external ids (issue awslabs#367) + added support for endpoint+region (e.g., STS via VPC)
c0be0cb
to
1295088
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good
+ added `ENDPOINT_REGION` nested key for a simpler Cx experience + deduplicated, and improved, logic w.r.t. CredentialsProvider construction to NOT swallow Exceptions
A new simpler option now exists for STS-via-VPC:
With this, a Cx only needs to provide the region (e.g., |
I have a general question, how can customers find out all the supported property kv pairs that can provided to MultiLangDaemon and what the valid values are? I see your detailed javadoc for NestedPropertyKey, but I as a customer would not know to look there unless I read the code. I see MultiLangDaemon has javadoc for the minimum properties that must be passed in. |
@@ -0,0 +1,93 @@ | |||
# The script that abides by the multi-language protocol. This script will |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this used only for test, can it be in src/test/resources?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Absolutely, and the correct thing to do; was an oversight in folder assignment. Thanks!
@@ -200,4 +198,9 @@ public void testPropertyValidation() { | |||
} | |||
} | |||
|
|||
@Test | |||
public void testActualPropertiesFile() throws Exception { | |||
new MultiLangDaemonConfig(FILENAME); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is this testing? Just constructor works fine?
Maybe we want to assert constructed instance is not null?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is this testing? Just constructor works fine?
I added Javadoc. Snippet: "catch any issues which might arise if there is a discrepancy between reality and mocking".
Maybe we want to assert constructed instance is not null?
assertNotNull(...)
gets marked as redundant because the construction is guaranteed non-null iff an Exception is not thrown.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But if you dont assert and the test throws exception it may not show as failed, isnt it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it does mark the test failed, so this is okay.
Yes, discoverability is an issue. This will be addressed by the following:
If you have further questions/suggestions about the discovery process, let's bring that conversation internal so I can share more details. I believe we're aligned in wanting to equip our KCL Cx to self-service (and make it easy for Cx to contribute new use cases). |
Issue #, if available:
#367
Description of changes:
[#367] Enhanced multi-lang
AWSCredentialsProvider=...
decoder and construction.mvn clean verify
yields:By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.