-
Notifications
You must be signed in to change notification settings - Fork 4k
Add new cmdlets for AzureDataTransfer #27926
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
base: main
Are you sure you want to change the base?
Conversation
Azure Pipelines successfully started running 3 pipeline(s). |
@fzkhan Please upload the generate-info.json file to fix the build issue. |
This PR was labeled "needs-revision" because it has unresolved review comments or CI failures. |
@vidai-msft I was following this wiki to generate the cmdlets and it did not output a On the same note, I see a comment in the wiki that says:
Is that also a file we have to add manually? So far, the only file I have added on my own is the |
The generate-info.json is generated by running build-module.ps1. If you do not see the file, please upgrade your autorest.powershell version to get the new feature. |
I updated to the latest version. But still not getting any additional files. Here is the
Ran |
Can you share the detailed steps? |
@vidai-msft I have renamed it to DataTransfer. But:
|
@vidai-msft Able to get around the testing failure now. Please let me know how to generate the file as I still am not able to get the commands to output it. |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
|
@fzkhan Where did you see the output? From PowerShell console or markdown file? |
@vidai-msft This is from the PS window after running |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
Description
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.md
and reviewed the following information:ChangeLog.md
file(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
.## Upcoming Release
header in the past tense.ChangeLog.md
if no new release is required, such as fixing test case only.