[GitHub] chetanmeh commented on issue #3412: Changes to runtimes variables in support of retiring 'whisk/*' runtimes
chetanmeh commented on issue #3412: Changes to runtimes variables in support of retiring 'whisk/*' runtimes URL: https://github.com/apache/incubator-openwhisk/pull/3412#issuecomment-374636516 > Ideally in this scenery, one would use ‘shell:’ to invoke an entry point in the invoker jar to dump the JSON to stdout. Makes sense. We can add a utility main class in common (implemented in java to avoid scala dependency in classpath) to dump the config. And in ansible just invoke ``` java -cp typesafe-config.jar:openwhisk-common.jar whisk.utils.ConfigDumper /path/to/output.json ``` This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] chetanmeh commented on issue #3412: Changes to runtimes variables in support of retiring 'whisk/*' runtimes
chetanmeh commented on issue #3412: Changes to runtimes variables in support of retiring 'whisk/*' runtimes URL: https://github.com/apache/incubator-openwhisk/pull/3412#issuecomment-374636516 > Ideally in this scenery, one would use ‘shell:’ to invoke an entry point in the invoker jar to dump the JSON to stdout. Makes sense. We can add a utility main class in common to dump the config. And in ansible just invoke ``` java -cp typesafe-config.jar:openwhisk-common.jar whisk.utils.ConfigDumper /path/to/output.json ``` This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
