Updating Cloud Build Repository Host Connection with new GitLab access token

[undef]

Hi!

I have next setup: Google Cloud Build has configured and working Host Connection to private GitLab repo through GitLab project token. Cloud Build Trigger successfully works, building my application. In fact, I have multiple triggers connected to different repos in one GCP project.

Project token for one of the repositories is about to be expired (in 7 days). So the general question is: what is the recommended course of actions in this situation?

I assumed, that I would need to generate new project token for respective GitLab repo (easy) and put it somewhere in GCP, but:
0. I couldn't find anything that could help me in Cloud Build web-interface.
1. Obviously, my attempts to find the solution on my own failed.
2. Cloud Build documentation tells me that those secrets are stored in Secret Manager, and I'm sure I can see them. But there are too many, I can't identify the correct one. I can't relate names of secrets like this `cloudbuild-gitlab-1715692777405-api-access-token` to a Host/Repository connection. So if I should just add new value of a secret, how do I identify the correct secret?

I understand, that I can just create new Host/Repository connection and make my trigger use it instead of the old one, but it seems like an overkill.

Please, help me to navigate this situation. Thank you in advance.

[undef · Accepted solution]

Apparently, this is just a bad web UI, because I was able to identify specific secret through Cloud Shell using combination of
```
gcloud builds connections list ...
gcloud builds connections describe ...
```