You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* working image download progress
* adding reporting download progress logic
* adding image recording test
* adding marketplace test
* Use fixed autorest.powershell version to generate
* updating env and recording files
* Revert change to README.md
* updatig variables and image recording
* image test
* storage path test
* disk recording
* updating env variables
* logical network test
* nic test
* fixing networkinterface test
* vm test
* fixing image test
* image recording
* fixing image
* fix
---------
Co-authored-by: Harika Vedati <[email protected]>
Co-authored-by: Lei Jin <[email protected]>
Co-authored-by: Jin Lei <[email protected]>
This directory contains examples from the exported cmdlets of the module. When `build-module.ps1` is ran, example stub files will be generated here. If your module support Azure Profiles, the example stubs will be in individual profile folders. These example stubs should be updated to show how the cmdlet is used. The examples are imported into the documentation when `generate-help.ps1` is ran.
3
+
4
+
## Info
5
+
- Modifiable: yes
6
+
- Generated: partial
7
+
- Committed: yes
8
+
- Packaged: no
9
+
10
+
## Purpose
11
+
This separates the example documentation details from the generated documentation information provided directly from the generated cmdlets. Since the cmdlets don't have examples from the REST spec, this provides a means to add examples easily. The example stubs provide the markdown format that is required. The 3 core elements are: the name of the example, the code information of the example, and the description of the example. That information, if the markdown format is followed, will be available to documentation generation and be part of the documents in the `..\docs` folder.
0 commit comments