ricardozanini commented on issue #1621: URL: https://github.com/apache/incubator-kie-issues/issues/1621#issuecomment-3057744571
> What’s the point of accepting a gen-manifest path in the kn workflow create command, when you can immediately run kn workflow gen-manifest afterward? It feels like duplicating the same functionality. To me, it seems a shortcut worth adding to the `kn workflow create` command. It can be a boolean flag to whether generate the manifests or not > The kn workflow run command is meant for running Quarkus locally in the current project to speed up development and debugging, there’s no need to supply a gen-manifest directory there. Not quarkus, but the workflow within a container. This I agree, no need to gen manifest while _running_ the app > The kn workflow deploy command already lets you point to a pre-generated manifest via the --custom-manifests-dir option. Again, `kn workflow deploy` should not have the `gen-manifest`. I agree to that. @masayag since you use this tool the most, mind weighing in? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
