Add experimental argument to open logs folder

[Trenly]

• Have you signed the Contributor License Agreement?
• Are you working against an Issue?
  • Open log files or provide path as output #2355 (comment)

---

Microsoft Reviewers: Open in CodeFlow

[denelon]

Does this argument work with any command? Does it display the help across all commands? Maybe a quick spec would make sense for this one. I'm expecting we need to think about how it would interact with the PowerShell cmdlets as well.

[Trenly]

Does this argument work with any command?

Yes

Does it display the help across all commands?

Yes

Maybe a quick spec would make sense for this one. I'm expecting we need to think about how it would interact with the PowerShell cmdlets as well.

I think it would be a good consideration, but I would suggest instead speccing out all common arguments; How does verbose logs interact with the cmdlets? How does wait interact?

I also think this could be refined more in the future (hence only mentioning the linked issue, not marking it for closure) as how users interact with logs is a complex subject. I was thinking build in some minimal functionality first, then spec out a larger feature around it?

[denelon]

Maybe it should be an experimental argument initially then. It allows us to get feedback before releasing it with the GA client if we need to iterate.

[denelon]

Yes, I agree we should cover the other types of arguments as well as they relate to PowerShell.

[Trenly]

Maybe it should be an experimental argument initially then. It allows us to get feedback before releasing it with the GA client if we need to iterate.

Made it experimental

[yao-msft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).