squakez commented on PR #4038:
URL: https://github.com/apache/camel-k/pull/4038#issuecomment-1424125601
Having a look at Kustomize, I guess we can try to apply the same principles.
So, for instance, we could have an Integration like the below:
```
apiVersion: camel.apache.org/v1
kind: Integration
metadata:
name: test
spec:
...
traits:
container:
port: 1234
```
and a Kustomize like configuration (ie, `prod-traits.yaml`) as below:
```
apiVersion: camel.apache.org/v1
kind: Integration
metadata:
name: test
spec:
traits:
container:
port: 6789
```
We can think of `kamel run ... --kustomize xyz.yaml` and `kamel promote ...
--kustomize xyz.yaml` that would take care to merge the content of the second
into the first one. I was having a look at the Kustomize dependency API and I
wonder if it makes sense to us it at all. I think we can simply have the same
result by applying a merge on our own before pushing the resource to the
cluster (it could work both when running the first time or promoting where the
operator create a copy of the source integration).
@lburgazzoli wdyt?
--
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]
