squakez commented on issue #5981: URL: https://github.com/apache/camel-k/issues/5981#issuecomment-2543123387
First of all thanks for the effort to put on a draft @cfitzw, really appreciated. About the specific problems you're mentioning: 1. Indeed, we cannot transform the usage of path as it introduce a compatibility problem. What we can do, however, is to introduce a new one, ie, `paths` that will hold the new logic. Eventually we can deprecate `path` in favor of `paths` if we see it makes sense. 2. If the goal of the feature is to support multiple paths and hosts, then, we may rework entirely the feature and allow the user to introduce a given syntax, eg, `-t ingress.rules=foo.bar.com/bar -t ingress.rules=*.foo.com/foo` which would translate into the Ingress structure you've highlighted. I am not entirely sure what exactly you need to support, but I think we can separate this issue to work both on 1 and, if that makes sense, on 2, providing a different parameter for each feature we want. -- 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: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
