This SAS KB article provides instructions about how to gather the information that is necessary to debug connectivity issues to Azure GIT repositories.
Complete these steps to gather output data:
1. Execute the following command to get an unencoded token:
kubectl -n <namespace> get secrets/sas-risk-cirrus-core-secret-xxxx --template={{.data.SAS_RISK_CIRRUS_CODE_LIB_REPO_TOKEN}} | base64 -d
2. Shell into the sas-risk-cirrus-core pod and run the following commands, replacing UNENCODED_TOKEN in the command with the unencoded token that you retrieved from step 1:
echo 'echo $SAS_RISK_CIRRUS_REPO_GIT_TOKEN' > /tmp/.git-askpass
chmod 700 /tmp/.git-askpass
export GIT_ASKPASS=/tmp/.git-askpass
export SAS_RISK_CIRRUS_REPO_GIT_TOKEN=UNECODED_TOKEN
git ls-remote {scheme}://{userid}:{path}/{path to repo}
export SAS_RISK_CIRRUS_REPO_GIT_TOKEN=
rm /tmp/.git-askpass2
3. Upload the output data to SAS Tech Support for review. For instructions, see How to upload and download files using the SASTSDrive file sharing server.
If the previous steps did not reveal the root cause, enable verbose and trace debugging as follows:
Shell into a running pod container (sas.risk.cirrus.core) and run the following code:
GIT_CURL_VERBOSE=1
GIT_TRACE=1
git ls-remote {scheme}://{userid}:{path}/{path to repo}
Gather the following configuration files for further review:
cat ~/.gitconfig
git config --global credential.authority basic
git config --list --show-origin --show-scope
Then, upload the output and configuration files to SASTSDrive.