cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2010
Views
1
Helpful
3
Replies
Highlighted
Beginner

Private GitHub Repo's

Pulling files into your app from a raw, public GitHub path is easy.  But for private repo's we need to use a personal token.  Has anyone been able to successfully configure a CloudCenter repo pointing at a private GitHub repo and pull those files into your CloudCenter app?  Token, SSH key/cert or otherwise?

Thanks!

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Cisco Employee

Michael,

We are going to release a CICD dCloud lab that has Jenkins/Artifactory/GitLab (not GitHub) integrated. The communication between Jenkins & GitLab will be token-based, as is the communication between the local repo and the remote GitLab repo. I could share the details with you privately if you would like. Does that satisfy your use case or are you thinking of something different?

View solution in original post

3 REPLIES 3
Highlighted
Cisco Employee

Michael,

We are going to release a CICD dCloud lab that has Jenkins/Artifactory/GitLab (not GitHub) integrated. The communication between Jenkins & GitLab will be token-based, as is the communication between the local repo and the remote GitLab repo. I could share the details with you privately if you would like. Does that satisfy your use case or are you thinking of something different?

View solution in original post

Highlighted

Hi Tuan,

Thanks for the reply.  Yes, please send what you have and hopefully I can figure it out from there.

Thanks!

Highlighted
Beginner

If you want to directly refer to a private github file from CloudCenter, what you could do is specify a command to download the file, then pipe it to bash. The command to download the file can be found here:

curl - How can I download a single raw file from a private github repo using the command line? - Stack Overflow

Don't use the -O option though, as that saves the file. Instead so something like

<command to download using token> | bash

All of that would go into the lifecycle action field using the choice "Command or URL"

This widget could not be displayed.