Declarative API Token Creation using GitOps?

[joshwright10]

I am in the process of implementing a few scripts in our CI/CD pipelines which can do things like trigger a sync to the Preview Environment Application once the Pull Request Branch has been updated, as I was finding that there was a long delay for the change to become active.

Ideally, I could use the Argo CD API from the pipeline agent to trigger the sync.
I was hoping that I could generate the automation service account in Argo CD as a local user using the declarative setup and use External-Secrets PushSecret to push the API Token from the cluster to a Key Vault which the Pipeline would then read to make API calls.

It seemed simple and fairly tidy in theory, but it seems that it is not possible to cleanly automate the API Token creation.

I see that there are a few PRs and Issues open regarding this, but they are old. E.g. #9884

Is there any new guidance or update to this process?
I couldn't find much documentation about setting up automation accounts for API access, other than using the argocd cli or doing it through the UI.