-
Notifications
You must be signed in to change notification settings - Fork 911
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
xpkg init provider-template-upjet
does not result in a buildable repo
#5789
Comments
Note this scenario works when using just a regular
|
I would like to work on this issue |
awesome @EraKin575, thank you! I have assigned you to the issue now as you get started. Let us know if you need any support 😉 |
|
Hi, @jbw976 ! I am able to reproduce the issue. It is going into the endless loop but I can't seem to find the "not a git repo" issue |
The problem you've described arises because you have not registered the submodule in the local git repository. After you've initialized a git repository, delete the build folder and execute the following command. You have to be present within the directory.
The build folder gets synced and populated now. Now, if you execute the make command, it will work. However, if you have not committed anything yet to the git repo, you will come across this message. Your command will still work. After making at least one commit to the git repo, this error will not be seen again. I have linked a StackOverflow post that explains this issue. Ambiguous Argument Error StackOverflow Hope this helps! |
What happened?
I was just trying to use
xpkg init
to get a fresh start of https://github.com/crossplane/upjet-provider-template going locally. The command succeeds like so:But there appears to be something missing that is preventing this fresh local repo from being able to build and produce artifacts. Just running
make
fails because the local repo isnot a git repository
. After runninggit init
,make
will go into an endless loop ofInitial setup complete. Running make again . . .
:I believe this has to do something with the build submodule not getting populated, that folder is completely empty:
A couple areas to investigate more fully:
.git
dir and be a valid git repo?How can we reproduce it?
Repro steps:
What environment did it happen in?
Crossplane version: v1.16.0
The text was updated successfully, but these errors were encountered: