odubajDT
odubajDT
I guess this was already been done by this PR https://github.com/keptn/keptn/pull/8530
Resolved via https://github.com/keptn/keptn/pull/8530
According to investigation and consultation with @bacherfl we should be able to implement a feature, which checks if the content-type is `application/json` and if yes, it should try to unmarshal...
Putting this ticket back to backlog, as there are multiple questionmarks here
open questions: - How the `mode` should look like, where should it be placed? - Should it be a required parameter? If yes, there is a need to to implement...
Note: the team decided no to implement the mode feature as described in this issue. It should be enough to add information whether the upstream was provisioned to the ExpandedProject...
Looks good :) will re-run the integration tests and if it passes, we're good to merge :+1:
> Hi @odubajDT, I've added the discussed dependencies to an `UpgradeCmdHandler` struct here: https://github.com/eyskim/keptn/blob/f8dbdab1fe21bef9d0d18116df818560c6c09e56/cli/cmd/upgrade.go#L308-L313. As well, I've templated some potential test cases. If possible, I wanted to ask your thoughts...
## Research findings It is possible to introduce Keptn as Argo extension. In fact, using Keptn as Argo extension means installing it to the same cluster as Argo is installed...
Waiting for this library https://pkg.go.dev/sigs.k8s.io/custom-metrics-apiserver to bump k8s libraries to 0.29.x