-
-
Notifications
You must be signed in to change notification settings - Fork 46
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
Issues with private registry github app #1431
Comments
Did you install the app in your github organization? |
Yep we did ! We give it privileges to all repositories |
Did you use command for the private key?
|
yep we did ! and put the output key from pkcs8.key into the terrakube VCS provider |
Can you create a workspace using the github app and run a plan just to check if the connection is working correctly? If the connection is working propertly it should download the github repository content |
I just created a VCS workspace, set default path as / in the repository, there is no terraform at the root of the repository but I suppose it tells us that the vcs connection is working correctly ? |
Use some folder that has some terraform file, run a That should be enough to see if the connection is cloning the repository correctly |
Can you try creating a module again? From the above it looks like the github app token is working correctly |
The creation of the module works fine ! When I create it it sees all tags however, when i create a new one after the module creation on terrakube, it seems like terrakube never sees it :/ |
I think maybe Terrakube generates the github token correctly when you create a workspace, after creating one workspace your modules creation should work. I guess there is some logic missing to generate the token if you create a module right after the VCS connection is created |
Just to clarify @BenjaminDecreusefond , module creation is working fine after you tested the workspace creation, right? |
The module creation was working fine before the workspace creation. The issue that I had and that i still have is that now, my module is created on Terrakube with all tags present on the repository. However, if now I push a new tag, Terrakube will never see and don't update the tag list. |
XD now I get it sorry You won't be able to see new tags immediately there is an internal job that refresh tags every five or three minutes |
Oh ! It's been 4 hours 😅 |
It is related to this issue from some time ago |
Do you think the error
could have an incidence ? |
Hey @stanleyz do you have any idea about this one? it looks related to the changes related to github app in this class
It looks like a bug but I am not sure |
Happy to help if needed ! :) |
By the way using oAuth app should work for you as a work around for now |
Yep, thank you I think that's what we're going to do for now ! |
Great ! I can confirm you it works like a charm with Oauth app ! thanks you very much ! |
FYI #1096 |
looks like so, will take a look later. |
Ah ok I didn't know sorry ! |
Feedback
Hi!
We are trying to set up the private registry with a github app and we are facing issue regarding the app.
We followed this https://docs.terrakube.io/user-guide/vcs-providers/github-app to create the VCS provider with the following parameter
we then followed this https://docs.terrakube.io/user-guide/private-registry/publishing-private-modules to set up the module. We set the following parameter
When we validate the config it creates the module with the version already present, however when we create a new tag version it is never taken into account by the module and never appear in the UI and we keep having this log in the API logs
It is very strange and we have trouble identifying where it could come from ?
Do you have any clue for us please ?
Regards ! :)
The text was updated successfully, but these errors were encountered: