Release process inconsistency

[raandree]

Problem description

Every now and then a access token expires and the a release does not succeed. This is usually not a big deal. But sometimes the PowerShell Gallery token is valid but not the GitHub one. This results in a release on the PowerShell Gallery but Sampler fails to write the tag in the GitHub repository. In this case, no further release will be possible until you create the tag manually.
Can we check the validity of the token for the PowerShell Gallery and GitHub first somehow and only proceed if both tokens are valid?

[gaelcolas]

First thoughts on this...

Testing the GitHub token might be easy (easier at least), so the process could be:

• If we test GH Token first, fail if access is denied
• Try Push to PS Gallery (validating the gallery)
• if that works, then create the tag

This should with minimum code and workflow change improve that experience.

[kilasuit]

Alternatively you could reset both tokens at the same time & create new ones using the same validity period (so not to have this headache) & have another workflow either here or elsewhere that acts as a reminder by creating an admin task as such to perform an update to those tokens. This then can be called if there is a failure, as well as being scheduled to run prior to them expiring. More work to do but probably worthwhile doing.