Skip to content

Added deprecation message to Invoke-AzStorageSyncFileRecall #14637

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

Merged
merged 1 commit into from
Mar 29, 2021
Merged

Added deprecation message to Invoke-AzStorageSyncFileRecall #14637

merged 1 commit into from
Mar 29, 2021

Conversation

mikefrobbins
Copy link
Contributor

Description

Added deprecation message to Invoke-AzStorageSyncFileRecall

Checklist

  • I have read the Submitting Changes section of CONTRIBUTING.md
  • The title of the PR is clear and informative
  • The appropriate ChangeLog.md file(s) has been updated:
    • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
  • The PR does not introduce breaking changes
  • If applicable, the changes made in the PR have proper test coverage
  • For public API changes to cmdlets:
    • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
      • {Please put the link here}
    • the markdown help files have been regenerated using the commands listed here

@@ -10,6 +10,9 @@ schema: 2.0.0
## SYNOPSIS
This command recalls all tiered files back to local disk.

> [!IMPORTANT]
> `Invoke-AzStorageSyncFileRecall` is deprecated. Please use [Invoke-StorageSyncFileRecall](/azure/storage/files/storage-sync-how-to-manage-tiered-files#how-to-recall-a-tiered-file-to-disk).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @mikefrobbins , the link for Invoke-StorageSyncFileRecall seems broken, please replace it with a valid link.

@mikefrobbins
Copy link
Contributor Author

@BethanyZhou It's a relative link and works once published to docs as shown in the 5.7.0 version. Using a relative link is recommended because it also works in air-gapped environments.

@BethanyZhou
Copy link
Contributor

Got it. LGTM. Thanks.

@erich-wang
Copy link
Member

Force merge because of known CI issue.

@erich-wang erich-wang merged commit 4307ec3 into Azure:master Mar 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants