squakez opened a new pull request, #4621: URL: https://github.com/apache/camel-k/pull/4621
<!-- Description --> This PR addresses a few enhancements which are helping GitOps or in general deployment operations. They are following up the some limitations founds in the proposed [Camel K GitOps strategy](https://camel.apache.org/blog/2023/07/camel-k-gitops/). First of all, we get rid of the destination checks when in dry-run mode. Second, we introduce a simple flag which helps putting in place any unopinionated deployment strategy, for example: ``` $ kamel promote test -i --to test 10.110.251.124/default/camel-k-kit-cj1ra5e9j3ks738a7bbg@sha256:99835a5da746fc3d7f96d0ae50c64df0e29eb3e8d131e61bfdfd617fdaa078ba ``` Finally we allow to specify the operator ID tenant which must be used to take care of the promoted integration, ie `kamel promote test -x my-production-operator-id --to test` Closes https://github.com/apache/camel-k/issues/4534 Closes https://github.com/apache/camel-k/issues/3890 <!-- Enter your extended release note in the below block. If the PR requires additional action from users switching to the new release, include the string "action required". If no release note is required, write "NONE". You can (optionally) mark this PR with labels "kind/bug" or "kind/feature" to make sure the text is added to the right section of the release notes. --> **Release Note** ```release-note feat(cmd): improve `kamel promote` ``` -- 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
