squakez commented on code in PR #3674:
URL: https://github.com/apache/camel-k/pull/3674#discussion_r980835796
##########
e2e/namespace/install/cli/promote_test.go:
##########
@@ -107,6 +107,21 @@ func TestKamelCLIPromote(t *testing.T) {
Expect(IntegrationPodImage(nsProd,
"promote-route")()).Should(Equal(IntegrationPodImage(nsDev, "promote-route")()))
})
+ t.Run("plain integration promotion update", func(t
*testing.T) {
+ // Update the configmap
+ var cmData = make(map[string]string)
+ cmData["my-configmap-key"] = "I am production,
but I was updated!"
+ UpdatePlainTextConfigmap(nsProd, "my-cm",
cmData)
+
+ Expect(Kamel("promote", "-n", nsDev,
"promote-route", "--to", nsProd).Execute()).To(Succeed())
Review Comment:
Yeah, finally I opted for this solution. When a user is doing a `promote`
probably knows what he is doing (similar when he `run` an integration that will
update any previous one). Definitely, we should add some output to tell the
user either the Integration was created or updated (such as when we `run` them).
--
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]
