'operation' fiels in ApplicationSets
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24.2k
- Forks
- 7.9k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 239
Description
# Summary
ApplicationSets need addition `spec.template.operation` fields to then inject it within the created Applications. Currently, in the `spec.template` of an ApplicationSet, `operation` is not available as for Applications (check CRD).
# Motivation
These `operation` fields are used for a range of things, as for force syncing for example, see the following [issue](https://github.com/argoproj/argo-cd/discussions/5172). I currently have to duplicate my Application manifests for different clusters instead of using ApplicationSets when I need this field.
# Proposal
Adding the said `operation` fields in the CRD and adapt the `applicationset-controller` consequently.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the ApplicationSet CRD definition and the applicationset-controller handling of spec.template, then compare the operation fields available on Applications. Done means the CRD accepts the fields and generated Applications receive them; add or update focused controller tests if existing tests cover this generation path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100