search

eclipse-pass / main

Catch all repository against which issues of general, cross cutting topics are logged.
Apache License 2.0
4 stars 8 forks source link

Document how to manage PAT organization secrets for access to multiple repositories #867

Open markpatton opened 10 months ago

markpatton commented 10 months ago

What?

As a developer, I want to know how to create a PAT secret in the organization that allows write access to multiple repositories.

Why?

Currently the JAVA_RELEASE_PAT is a classic personal PAT in the main repository that has to be created by a developer. Ideally it would be a PAT managed by the organization instead.

How?

This may involve creating a ticket for Eclipse.

Acceptance Criteria

This should be documented in dev/release-steps-with-automations.md by updating the section about the JAVA_RELEASE_PAT.

Related Issues

aforward commented 10 months ago

I have asked EF about the management of Fine-Grained tokens (link below for my reference but not accessible to others)

https://gitlab.eclipse.org/eclipsefdn/infrazilla/-/issues/1483

GitHub is (slowly) deprecating the use of classic Personal Access Token as a means to automate actions via their API.  Our eclipse-pass organization would like to move towards using [Fine Grained Tokens](https://github.com/settings/tokens?type=beta), but these tokens expire which would result in additional management.
Here are a few questions

Do you recommend Fine Grained Tokens, or should we stay with Personal Access Tokens until Fine Grained is out of Beta?

If we go with Fine Grained, then what is the process to have it generated (created a ticket with the necessary permissions)?  
And how is the cycling of new tokens managed?

How can we use Otterdog to help automate this process (or can we, as the secrets are created internally at Eclipse Foundation)?