404 for actions for Application in non-argocd Namespace

[mikebryant]

Checklist:

• I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
• I've included steps to reproduce the bug.
• I've pasted the output of argocd version.

Describe the bug

We're trying to make use of the actions functionality for Deployments / StatefulSets restarts.
This works fine in Applications that live in the argocd Namespace, but we're making use of the application.namespaces feature, and in apps in other Namespaces the actions aren't visible.

Using the network debugger, we see requests getting a 404, e.g. https://argocd.example.co.uk/api/v1/applications/web-server/resource/actions?namespace=test-ns&resourceName=web-server&version=v1&kind=Deployment&group=apps

It looks like the Namespace of the Application isn't being used in the url path

To Reproduce

Set up an Application in a Namespace other than argocd

Expected behavior

The UI should hit the right backend url, and display the actions

Screenshots

Version

Paste the output from `argocd version` here.
Not available due to https://github.com/argoproj/argo-cd/issues/9747 - not possible to log into the server using non-core mode in our setup

These are the docker images in use
✗ kubectl get pod -o yaml | grep image: | sort | uniq
      image: ghcr.io/dexidp/dex:v2.35.3
      image: public.ecr.aws/bitnami/redis-exporter:1.45.0
      image: public.ecr.aws/docker/library/redis:7.0.5-alpine
      image: quay.io/argoproj/argocd:v2.5.7

Logs

Paste any relevant application logs here.