Skip to content
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.

Sign up for GitHub

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

Jump to bottom

platyPS workflow doesn't support configuration #336

Closed
BernieWhite opened this issue Jan 22, 2018 · 4 comments
Closed

platyPS workflow doesn't support configuration #336

BernieWhite opened this issue Jan 22, 2018 · 4 comments
Labels
Issue-Enhancement Issue is more of a feature request than a bug Resolution-Declined The proposed feature is declined.
Milestone
Future-Consider

Comments

@BernieWhite
Copy link
Contributor

It would be nice if platyPS supported saving default configuration to a file like yaml similar to other dev ops pipeline tools instead of specifying switches on each update/merge/new command.
@vors
Copy link
Collaborator

vors commented Jan 22, 2018

Yes, totally

@BernieWhite
Copy link
Contributor Author

#345

@theJasonHelmick theJasonHelmick added this to the Future-consider milestone Jan 22, 2021
@sdwheeler
Copy link
Collaborator

This is easily managed using splatting. Can you describe a more specific scenario that couldn't be solved by splatting?

@sdwheeler sdwheeler added Issue-Enhancement Issue is more of a feature request than a bug and removed Feature Request labels Apr 5, 2022
@sdwheeler sdwheeler mentioned this issue Apr 11, 2022
Closed
@sdwheeler sdwheeler added the Resolution-Declined The proposed feature is declined. label May 31, 2024
@sdwheeler
Copy link
Collaborator

Need to understand the scenario better. The workflow is totally changing in the Microsoft.PowerShell.PlatyPS v1 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Enhancement Issue is more of a feature request than a bug Resolution-Declined The proposed feature is declined.
Projects
None yet
Milestone
Future-Consider
Development

No branches or pull requests
4 participants
@vors @theJasonHelmick @BernieWhite @sdwheeler