Updates documentation of flow export command. Closes #6418#7244
Updates documentation of flow export command. Closes #6418#7244nanddeepn wants to merge 11 commits into
flow export command. Closes #6418#7244Conversation
pnp#7233 Co-authored-by: Copilot <copilot@github.com>
There was a problem hiding this comment.
Pull request overview
Updates the CLI documentation for m365 flow export to more precisely describe what the --format json output represents (an ARM template JSON), aligning user expectations with the actual exported artifact.
Changes:
- Refined the JSON export example description to state that it exports the flow’s ARM template as JSON.
| ``` | ||
|
|
||
| Export the specified Power Automate flow as a JSON file | ||
| Export the ARM template of the specified Power Automate flow as a JSON file |
|
Thanks, we'll try to review it soon! |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Waldek Mastykarz <waldek@mastykarz.nl>
|
hi, due to a patch release, we needed to perform we had to rebase the main branch, which now makes this PR out of sync with the latest state of main. |
|
Hi @Adam-it Can you please help with any commands to rebase? Or I can create another pull request |
|
Hi @nanddeepn, have you tried this approach? Otherwise we can rebase it for you if you have struggles. |
|
Thank you @milanholemans |
Closes #6418
Updated the documentation for the
flow exportcommand to clarify the output format when exporting as JSON. The description now specifies that the command exports the ARM template of the specified Power Automate flow as a JSON file, rather than just a generic JSON export.