After discussing with @JamesWTruher , it may be possible for crescendo to enumerate the help of some modern native commands to autogenerate the configuration file with parameters and help. Modern native commands that emit their help as structured data (i.e. xml, json) such as Docker or Kubectl, could use this information to generate the configuration file.
This would decrease the development time for more complex commands, and increase the command parameter coverage - allowing the module author to focus on cmdlet design and output handling.
This could be added to Export-CrescendoCommand:
-OriginalCommand - path and executable of the native command
-Verb - Desired verb of the new cmdlet
-Noun - Desired noun of the new cmdlet
After discussing with @JamesWTruher , it may be possible for crescendo to enumerate the help of some modern native commands to autogenerate the configuration file with parameters and help. Modern native commands that emit their help as structured data (i.e. xml, json) such as Docker or Kubectl, could use this information to generate the configuration file.
This would decrease the development time for more complex commands, and increase the command parameter coverage - allowing the module author to focus on cmdlet design and output handling.
This could be added to Export-CrescendoCommand: -OriginalCommand - path and executable of the native command -Verb - Desired verb of the new cmdlet -Noun - Desired noun of the new cmdlet