Standardized aws: [ERROR]: format for all CLI error messages #9889
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
AndrewAsseily
changed the title
AndrewAsseily
changed the base branch from
nyandrew/str-std-error
to
feature/str-std-error
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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: CLI-7288
Description of changes: Standardizes all AWS CLI error messages to use the format
aws: [ERROR]: <error-message>.Behavior:
Before:
After:
Backward Compatibility
Error message content is preserved exactly. Only the prefix changes from
error:to[ERROR]:. Scripts parsing error content should continue to work with minimal modifications.Description of tests: