Project Permissions added after AppSet is created aren't picked up by the AppSet

[claire-fletcher]

Checklist:

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

Describe the bug

We created an AppSet with a cluster generator and then realised that the project it was associated with did not have permission to deploy into the correct cluster for one of the applications the AppSet was trying to generate. We then went and added this permission in our code, synced Argo CD, and saw the new permission in the UI.

However, the AppSet was still stating project permission failures. It was only after a non-cascading delete of the AppSet that the new permissions were picked up and the error went away.

To Reproduce

1. Create an AppSet with a project that does not have permission to deploy into the cluster which the appset tries to generate.
2. Add the permission to the project
3. The app set still shows permission errors relating to the project

Expected behavior

When the project permission was added and seen in the UI, I expect the AppSet (with cluster generator) with an issue to now work as the project associated with it does have the permission it needed.

Version

v2.7.3+e7891b8.dirty

[andrii-korotkov-verkada]

ArgoCD versions 2.10 and below have reached EOL. Can you upgrade and let us know if the issue is still present, please?