Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
OPAL server failed to clone a private policy repo when OPALPOLICYREPOMAINBRANCH was set to a non-default branch (e.g. dev), with errors like did not find main branch. Cloning worked when the default branch was used, but a configured non-base branch broke the clone. The config used OPALPOLICYREPOMAINBRANCH=dev with a private repo over SSH.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
Upgrade OPAL to 0.1.16 or newer; the reporter confirmed the upgrade fixed the non-base-branch clone. The maintainer could not reproduce it on 0.1.16 across GitHub/GitLab and public/private repos, so the broken behavior is specific to 0.1.12 and earlier. The reporter's setup used a private repo, which the maintainer's 0.1.16 verification also covered. Source: https://github.com/permitio/opal/issues/150
Source: https://github.com/permitio/opal/issues/150
Shows how to fix oPAL cannot clone private repo with non-default main branch (fixed in 0.1.16). Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Shows how to fix oPAL cannot clone private repo with non-default main branch (fixed in 0.1.16). Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Shows how to give a Cloud Build step access to a private GitHub repository for Go dependency fetching.