100% this. A OCI/REPO provider credential source at Hub level would be very nice.

Thanks for the suggestion and support Sami and Brad. I will add this to the internal tracker and keep you both up to date. Definitely seems to be mounting interest for this!

This has been on my wishlist for a long time as well - I've got a handful of private repo credentials I keep having to manually add to each stack definition.

I concur that this would be a nice upgrade. Having to go look up that token every time I add a repo isn't the end of the world, but it is consistently annoying.

Oh to add a use case for the org wide credentials: Right now every single one of my stack definitions has the same username/password added to authenticate to the private repo where the json file defining the stack actually lives. That'd be nice to have handled a bit more globally, too.