A reusable workflow deploys correctly in the caller but silently loses its secret in the called workflow
The parent workflow has access to the credential, yet the called workflow behaves as if it is missing because the contract between caller and callee never passed it along.
CI/CDIntermediate
A reusable workflow inherits the caller repository but not its permissions, so the deployment step fails after modularization even though the old monolithic job worked
Community-field CI/CD problem inspired by GitHub reusable workflow issues where permission contracts changed after refactoring.
CI/CDAdvanced
An Argo CD repo-server trust update lands and one Git mirror still fails
The new known_hosts is correct, but one repo-server pod still sees the stale mounted cache from an older sidecar path.
CI/CDAdvanced
A GitHub deployment is approved and one environment still rejects the run
The promoted workflow exists, but one environment policy still matches the old reusable workflow reference after repository cleanup.