Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More Flexible App Selection in argocd-update Step #3576

Open
3 tasks done
wmiller112 opened this issue Feb 26, 2025 · 0 comments
Open
3 tasks done

More Flexible App Selection in argocd-update Step #3576

wmiller112 opened this issue Feb 26, 2025 · 0 comments

Comments

@wmiller112
Copy link
Contributor

Checklist

  • 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

It would be nice to be able to select applications to be managed by a stage with argocd-update step by more than just a complete name.

Motivation

We've found as we add and remove applications, whether that be from adding/removing services or adding/removing clusters that existing services then get deployed to (by way of new applications generated by applicationsets), that we need to have some custom way of generating the list of apps a stage should be responsible for. I've handled this using argocd lovely plugin with a preprocessor that basically performs the functions of the argocd applicationset git file generator to create a kustomize patch with all the app names. This is fairly cumbersome and seems like it shouldn't be necessary at least from a security perspective, if we're already granting a particular stage permission to sync the application via the required kargo.akuity.io/authorized-stage annotation on the app side.

Suggested Implementation

Ability to select applications for sync by label or regex of the name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant