Collaborate upstream to allow ArgoCD plugin to reference multiple applications in one Backstage resource

[tumido]

Additional context

We want to have only a single component of the same workload. Not a separate one per cluster. That's too much clutter. ArgoCD plugin for Backstage currently supports fetching multiple ArgoCD apps only if each of those apps is located on a different cluster. We need to be able to also query multiple applications from the same ArgoCD instance.

ArgoCD plugin by Roadie currently supports there annotations:

• argocd/app-name: Exactly matches ArgoCD app name (used to query /api/v1/applications/{name} endpoint
• argocd/app-selector: Selects ArgoCD instance in case multiple are mapped via proxy
• argocd/project-name: Selects ArgoCD project
• `argocd/proxy-url: Custom proxy url

We need to have argocd/app-name support some kind of selector, preferably something standard like selector query parameter for /api/v1/applications ArgoCD api endpoint.

See: https://argocd.operate-first.cloud/swagger-ui#operation/ApplicationService_List

Acceptance Criteria

• [ ] Multiple applications can be fetched for a single resource from single ArgoCD

Relevant links

https://argocd.operate-first.cloud/swagger-ui#operation/ApplicationService_List

https://github.com/RoadieHQ/roadie-backstage-plugins/blob/main/plugins/frontend/backstage-plugin-argo-cd/src/components/useAppDetails.ts

[sesheta]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[SamoKopecky]

/remove-lifecycle stale

[tumido]

/close

I favor of https://github.com/janus-idp/backstage-plugins/issues/162