We are working with ApplicationSet, but after v1.14.0breaking change we are facing issue with git authentications because repo-secret set with project field and ApplicationSet don't have any project field, and we can't remove project field from repo-secret.
Business Goal/Objective
Application deployments are affected due to breaking change.
Goals
ApplicationSet generators do need repoURL and we can't add repo accessible to everyone at ArgoCD level, we prefer project level isolation and would like to continue using it in ApplicationSet like it used to.
Requirements
Requirements
Notes
MVP
Use Cases
< What are we making, for who, and why/what problem are we solving?>
Out of Scope
<Defines what is not included in this story>
Dependencies
< Link or at least explain any known dependencies. >
Background and Strategic Fit
< What does the person writing code, testing, documenting need to know? >
Assumptions
< Are there assumptions being made regarding prerequisites and dependencies?>
< Are there assumptions about hardware, software, or people resources?>
Customer Considerations
< Are there specific customer environments that need to be considered (such as working with existing h/w and software)? >
Documentation/QE Considerations
< What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)? >
< Does this feature have a doc impact? Possible values are: New Content, Updates to existing content, Release Note, or No Doc Impact>
Impact
< If the feature is ordered with other work, state the impact of this feature on the other work >
Related Architecture/Technical Documents
<links>
Definition of Ready
The objectives of the feature are clearly defined and aligned with the business strategy.
All feature requirements have been clearly defined by Product Owners.
Normal