credential not working after update set promotion

[andrewcaldw]

Hi All,

So I have a question about how to work with a custom credential alias created for use with several custom actions that exist within the github spoke. In our developer environment I've created several custom actions that exist in the github spoke application and a credential alias with attached credential (see screenshots).

Everything works fine with this in our dev environment. When I promote the relevant update sets to our QA testing environment, everything shows up as it should, however the action to create a git branch (and all the other git actions in the related workflow) cannot authenticate to git. If I then go into the credential alias and click on the associated credential and paste in the API key, it all of a sudden works like a charm.

I wouldn't actually care about this much except I do not have access into our production environment so cannot correct the credential if it doesn't work once the update set is promoted to prod.

My question is, has anyone seen this before and been able to resolve it? It seems very weird to me that the value of the API key in the credential is not being captured in the update set, unless that is by design and needs to be manually set? (that seems counter intuitive to the whole update set/code promotion process).

Thanks,

Andrew