config file support #9
Comments
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story. The labels on this github issue will be updated when the story is started. |
This seems interesting as a more holistic solution to flag parsing. The only issue that jumps out immediately is |
@ljfranklin, the implication above is that it would be a backwards compatible change with Of course, when I say this, I do realize this would affect the interpolation that |
I don't have a good feel for whether this belongs in here, or if it'll take some time to gain alignment on the design. But if it's feeling like it's going to take time to hash out the design or decide, one option in the short term may be to first wrap jhanda in |
Right, I forgot that the config file that
Configuring via fileExample YAML:vm-extension-config:
name: some_vm_extension
cloud_properties:
source_dest_check: false But changing the top-level key in the |
The command line arguments being used in
om
sometimes represent large JSON payloads. For example, theconfigure-product --product-properties
. This command has added support for a--config
YAML file, so those command line arguments can be passed in -- over bash encoding a large JSON string.We were investigating adding this behaviour to other commands on
om
, too. Since,--config
file is mapping a file to command line arguments, we thinkjhanda
might be a great place to centralize this logic.Our team's proposal, is to have a special
ConfigFile
type for that if it exists on thestruct
will automatically load from the file.Better to show than tell. If we were to write a test.
The text was updated successfully, but these errors were encountered: