lburgazzoli commented on PR #4038:
URL: https://github.com/apache/camel-k/pull/4038#issuecomment-1424150738
I'm not very sure that what you are describing here is the right way of
using kustomize, what one would expect is to write something like:
```yaml
resources:
- integration.yaml
patchesJson6902:
- target:
group: camel.apache.org
version: v1
kind: Integration
name: test
patch: |-
- op: replace
path: /traits/container/port
value: 6789
```
So I would expect `kamel promote` to have an option to generate a yaml file
you can then post-process with kustomize.
The main point for me is that kustomize is pretty much the standard for post
processing resources as it is embedded in kubectl (i.e. kubectl applu -k) and
integrated by almost all the CD tools (ArgoCD, Flux, etc) so any other option
would make things a little special.
Btw, those are my 2c :) I think it would be perfectly possible to have both
the solution in place, but for the specific case of the #3891 a standard way
would be to leverage kustomize.
--
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]
