-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
{storage-preview} Add hns soft delete #2877
Conversation
storage-preview |
7581ccf
to
385a3f5
Compare
src/storage-preview/azext_storage_preview/operations/filesystem.py
Outdated
Show resolved
Hide resolved
src/storage-preview/azext_storage_preview/operations/filesystem.py
Outdated
Show resolved
Hide resolved
if pages.continuation_token: | ||
next_marker = {"nextMarker": pages.continuation_token} | ||
result.append(next_marker) |
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 noticed that in main repo, we add next_marker
to result or warning message according to --show-next-marker
. Why we don't need such parameter and just make adding to result as default behavior?
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.
as warning message is legacy method, to not break customer, we still keep it. Adding next marker in result will give customer better experience to get the marker value instead of parsing stderr.
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.
LGTM
Co-authored-by: Yishi Wang <yishiwang@microsoft.com>
This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines
azdev style <YOUR_EXT>
locally? (pip install azdev
required)python scripts/ci/test_index.py -q
locally?For new extensions:
About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update
src/index.json
automatically.The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify
src/index.json
.