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 feature request.
I've pasted the output of kargo version, if applicable.
I've pasted logs, if applicable.
Proposed Feature
With promotion steps, argocd meta info became stage agnostic so technically they belongs to individual promotions. But in most cases it rarely changes and logically it is safe to attach with stage meta. So proposal is to move back the ArgoCD deep links to top of Stage details view rather than in individual promotions column. Or we can keep at both places.
Motivation
Previously it was at top of stage view and is more accessible there rather than individual promotion steps.
Suggested Implementation
Reuse the logic of deep link construction in individual promotion for all promotions and show the list of links on top of Stage details view
The text was updated successfully, but these errors were encountered:
I feel like we might just want to remove the guesswork/inference, and just start using Stage annotations and be explicit about creating links based on the apps mentioned in the annotations.
Checklist
kargo version
, if applicable.Proposed Feature
With promotion steps, argocd meta info became stage agnostic so technically they belongs to individual promotions. But in most cases it rarely changes and logically it is safe to attach with stage meta. So proposal is to move back the ArgoCD deep links to top of Stage details view rather than in individual promotions column. Or we can keep at both places.
Motivation
Previously it was at top of stage view and is more accessible there rather than individual promotion steps.
Suggested Implementation
Reuse the logic of deep link construction in individual promotion for all promotions and show the list of links on top of Stage details view
The text was updated successfully, but these errors were encountered: