philips-software / app-token-action Goto Github PK

When creating a base64 encoded with certutil you will get a HEADER and FOOTER.

This will break the action.

Command

certutil -encode my.private-key.pem my.private-key.pem.base64encoded

HEADER

-----BEGIN CERTIFICATE-----

FOOTER

-----END CERTIFICATE-----

We had big problems using this because of lack of documentation anywhere:

Please add where to create a ticket to get an app created for the users repos (DOST)
What to request in the ticket
Where to modify the settings of the app (https://github.com/organizations/philips-internal/settings/apps)
How to generate the token (add secret -> base64 private-key.pem > base64->pem
What security settings to set
How this gets approved (email) -> link to update
What variables to add/set in the repo.

This took us 5 working days and a lot of effort to with multiple people.

It would actually be better if there was a default app for the entire organisation with organisation level tokens that could be used.

All dependabot PRs are failing.

This makes it very hard to keep this action up-to-date.

Node16 is deprecated and using the action results in warning annotation.

Hi there,

I would be happy to get some feedback from you on my implementation with a quite similar approach,WDYT?

Feel free to have a look at https://github.com/qoomon/github-actions-access-manager

On ubuntu:22.04:

error:25066067:DSO support routines:dlfcn_load:could not load the shared library

also refer to this github discussion

Rarely, we receive this transient error (on repos for which this is known to normally work)

Error: Cannot find installation for app with id: ***. Did you installed your app in a repo?

There are no other messages in the workflow logs.