-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Modify http cred provider resolving logic #4961
Merged
Merged
Changes from 12 commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
a71bedc
Modify and Merge http cred provider logic to allow link-local urls
f08fc0b
Add and Merge changelog for last commit
f4f3fc7
Modify and Merge http cred provider resolving auth token file
b4fc961
Modify and Merge changelog
d5735f7
Modify and Merge auth token file retrieve logic
0be20ae
Modify and Merge http cred provider logic
4755c89
Modify and Merge http cred provider syntax
ecfb8f5
Release v1.44.332 (2023-08-25) (#4965)
aws-sdk-go-automation 8e3829b
Release v1.44.333 (2023-08-28) (#4966)
aws-sdk-go-automation 807c9ee
Modify and Merge auth token file resolving logic
c8ccaaf
Release v1.44.334 (2023-08-29) (#4968)
aws-sdk-go-automation e3b83f4
Merge branch 'main' into feat-http-cred
460e716
Modify and Merge eks auth syntax
bcc4451
allow ipv6 eks host
lucix-aws 98515f3
Modify and Merge comment
47a4701
Modify and Merge comment format
7195c34
Update CHANGELOG_PENDING.md
lucix-aws 0b32bd7
Update CHANGELOG_PENDING.md
lucix-aws File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
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.
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 understand that short-hand is often effective in our own internal conversations. but with customer-facing release notes, lets use correct grammar with complete thoughts. Additionally, since this is more of a feature and not a simple bug fix, the language should emphasize the overall problem being solved.
The way this is written sounds like this PR is just fixing a bug. However, as i understand it, were actually adding a feature to the HTTP credential provider. Since this is a feature, and not merely a bug-fix, it should relate back to the higher-level problem. For example,
And this
This reads like a run-on sentence and sounds like its just explaining implementation details. And because its a run-on sentence, im not sure if
auth token directly set in env var
is something that already exists or is something that you are adding.Since most of the feature is explained in what I wrote above, you just add a clarification here for the motivation. For example: