Error for expired git credentials when creating release

[benPearce1]

Severity

Blocking some customers, but simple workaround available

Version

2023.2

Latest Version

None

What happened?

Using a project that is using Config As Code, when the git token/credentials expire or are incorrect API calls that rely on the git repo, such as Create Release, will error and return the Git auth error back as the response. This can be confusing as it appears that the Octopus API call failed but it may be the secondary Git call that fails.

This style of error would most likely be experience from integrations such as Azure Devops plugin, GitHub Actions tasks, TeamCity plugin etc.

It

Reproduction

N/a

Error and Stacktrace

No response

More Information

For a Git repo hosted on Azure Devops, the error can be returned as a HTML response with the error message embedded in it, for example:

Access Denied: The Personal Access Token used has expired

Workaround

Update your Git credentials.

[michelle-luana]

The Octopus engineering team has reviewed this issue.
After careful consideration, we’ve classed this low priority. This means we won’t work on it in the near future. We prioritize issues based on the number of people affected, the impact type, and available workarounds. If you’ve encountered this issue and haven’t informed our support team, please email [email protected]. Knowing how many people this issue affects helps us determine its priority.