Feature Overview

• Enable a view type that shows Git-managed resources within their respective resource trees, rather than only at the top level

Business Goal/Objective

• Improve resource visualization in ArgoCD to provide a clearer, more intuitive view of how Git-managed resources relate to their cascading resources
• Reduce cognitive load when navigating complex application structures
• Low-medium urgency: While most users don't have both parent and subordinate objects in Git, those who do would benefit from improved visibility

Goals

• DevOps engineers and platform administrators benefit from this feature by gaining a clearer visualization of resource relationships between parent and child resources that are both held in git. ArgoCD gains a clearer user interface and user experience.

Requirements

Use Cases

• DevOps engineers and platform administrators benefit from this feature by gaining a clearer visualization of resource relationships between parent and child resources that are both held in git.

Out of Scope

• Changing the underlying data model of how ArgoCD tracks resources
• Modifying how resources are handled or managed

Dependencies

• ArgoCD user interface

Background and Strategic Fit

• N/A

Assumptions

• The ArgoCD backend already has the necessary data to determine if a resource in a tree is also managed in git
• This will be a configurable change that does not affect the current user experience

Customer Considerations

• None, so long as current behavior (git-managed resources at root) is extended to include resource tree placement and not replaced

Documentation/QE Considerations

• Documentation should include how to access new view type
• Updates to existing content / Release Note

Impact

• This feature should have minimal impact, as it should primarily be a UI enhancement

Related Architecture/Technical Documents

• N/A

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.
• The feature has been broken