-
Notifications
You must be signed in to change notification settings - Fork 600
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
flux bootstrap git won't accept scp-style URLs #5015
Comments
I am running into this with Bitbucket Cloud. They also use the latter format. Update: Just saw in their docs that Bitbucket Cloud also accepts the format |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
There are a number of ways in which SSH URLs can be formatted, one of them is in "scp-style":
hostname:group/repo.git
, sometimes also written asssh://hostname:group/repo.git
, although the latter isn't to spec.Unfortunately,
flux bootstrap git
can handle neither of these.Meanwhile,
git clone
and (other) remote-modifying git commands work with both these urls. For reference, GitHub uses the former and GitLab the latter format, so they're both very established and all tools but Flux support them.Steps to reproduce
flux bootstrap git --url="<repo url in scp-style format>"
Expected behavior
Works like ssh urls in non-scp-style format
Screenshots and recordings
No response
OS / Distro
macos (arm)
Flux version
flux: v2.3.0
Flux check
► checking prerequisites
✔ Kubernetes 1.29.9 >=1.28.0-0
► checking version in cluster
✗ checking failed: customresourcedefinitions.apiextensions.k8s.io "gitrepositories.source.toolkit.fluxcd.io" not found
► checking controllers
✗ no controllers found in the 'flux-system' namespace with the label selector 'app.kubernetes.io/part-of=flux'
► checking crds
✗ no crds found with the label selector 'app.kubernetes.io/part-of=flux'
✗ check failed
Git provider
No response
Container Registry provider
No response
Additional context
From the git-clone manpage's git urls section:
Code of Conduct
The text was updated successfully, but these errors were encountered: