tchughesiv commented on issue #380: URL: https://github.com/apache/incubator-kie-kogito-serverless-operator/issues/380#issuecomment-1932685739
> Why we need to add `workflow` on top of it? @ricardozanini I thought this was what you asked for in https://github.com/apache/incubator-kie-kogito-serverless-operator/pull/372#discussion_r1474656365. There were 2 goals in mind - 1. Communicate, via the api, that workflows are the consumers of these cluster-wide platform settings. NOT services or any other future components. 2. Communicate, via the api, WHICH settings are being made available cluster-wide. Currently, that would be services... but there could be more in the future, e.g. build configs. Without `workflow`, i expect users will still have to rely on reading the api field description to understand that only workflow configs are affected. That said, its your call. -- 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]
