-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
cloudfront create-invalidation --paths #1662
cloudfront create-invalidation --paths #1662
Conversation
class PathsArgument(CustomArgument): | ||
|
||
def __init__(self): | ||
help = """The space-separated paths to be invalidated. |
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.
Don't shadow a builtin.
Overall looks good. It would be nice if we can somehow document that invalidation-batch and paths are mututally exclusive? Maybe we can just add a note in the help text of |
Thanks for the suggestion! "invalidation-batch and paths are mutually exclusive" is now added into the help text of --paths. And all other comments have been incorporated. |
class PathsArgument(CustomArgument): | ||
|
||
def __init__(self): | ||
doc = """The space-separated paths to be invalidated. |
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 would avoid using docstring quotes so something like this:
doc = (
'The space-separated paths to be invalidated.'
' Note: --invalidation-batch and --paths are mututally exclusive.'
)
Looks good. Had a few small comments. |
Thanks. Looks good! 🚢 |
Looks good. |
5942910
to
4169450
Compare
…aths cloudfront create-invalidation --paths I rebased my CHANGELOG just now. Now merging.
@rayluo If I run
why is invalidation-batch required? UPDATE: |
Now
aws cloudfront create-invalidation
has a new parameter--paths
.This fixes #920