You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've searched the issue queue to verify this is not a duplicate bug report.
I've included steps to reproduce the bug.
I've pasted the output of kargo version.
I've pasted logs, if applicable.
Description
Starting from version 1.1.0, we can use expr-lang in our Stage resources. More specifically, in the "config" section. This works well, including in the argocd-update step (Kargo is able to update the ArgoCD application successfully).
Also, for any app we have in argocd-update, Kargo is able to display a link that directs us to the ArgoCD application whenever we click on the stage in the UI. The problem is that the link contains the expr-lang references we put in the Stage resources, instead of displaying the final (after processing) link. This prevents us from going to the app, as the link is wrong.
Screenshots
Steps to Reproduce
Create a Stage which contains an argocd-update step with expr-lang references in the name. Example:
Again it traces back to #2752 that how far we stretch the flexibility for UI plugins.
An easy-ish interim solution is to get the namespaces/names of affected apps by looking at the health checks left behind by the Promotion. An argocd-update step, when successful, always leaves behind "instructions" for assessing App health to inform Stage health. Unlike the config passed to the argocd-update step, these would never contain expressions.
Checklist
kargo version
.Description
Starting from version 1.1.0, we can use expr-lang in our Stage resources. More specifically, in the "config" section. This works well, including in the
argocd-update
step (Kargo is able to update the ArgoCD application successfully).Also, for any app we have in
argocd-update
, Kargo is able to display a link that directs us to the ArgoCD application whenever we click on the stage in the UI. The problem is that the link contains the expr-lang references we put in the Stage resources, instead of displaying the final (after processing) link. This prevents us from going to the app, as the link is wrong.Screenshots
Steps to Reproduce
Create a Stage which contains an
argocd-update
step with expr-lang references in the name. Example:Version
The text was updated successfully, but these errors were encountered: