Uh oh!
There was an error while loading. Please reload this page.
generate: Add --output=PATH and write to stdout by default - #129
Conversation
This makes it easier to post-process output before writing it to disk. For example, you may want to make adjustments with jq and/or write part of the configuration to a different file for consumption by non-OCI tools [1]. [1]: opencontainers#128 (comment) Signed-off-by: W. Trevor King <wking@tremily.us>
liangchenye
commented
Jul 6, 2016
LGTM |
Mashimiao
commented
Jul 6, 2016
+1 |
grantseltzer
commented
Jul 6, 2016
I think having the default output be a file should remain the same. Maybe there should be an option to output to stdout, and an option to to rename the file output? It could be the same flag too, either a path or "STDOUT" possibly. |
wking
commented
Jul 6, 2016
On Wed, Jul 06, 2016 at 08:48:31AM -0700, Grant Seltzer Richman wrote:
I like having ‘--output PATH’ always mean “please write to the file at On the other hand, with the default-to-stdout approach, folks don't |
iamanush
commented
Jul 6, 2016
+1 I like the idea of defaulting to STDOUT and providing the --output flag for the file. |
mrunalp
commented
Jul 6, 2016
LGTM |
The switch to --output in 06d61a3 (generate: Add --output=PATH and write to stdout by default, 2016-07-05, opencontainers#129) was too narrow. There's no need to change directories now that the output path is configurable. Signed-off-by: W. Trevor King <wking@tremily.us>
This makes it easier to post-process output before writing it to disk. For example, you may want to make adjustments with jq and/or write part of the configuration to a different file for consumption by non-OCI tools.