Skip to content
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

how to configure existing repositories in a github org? #934

Open
sm43 opened this issue Oct 20, 2022 · 3 comments
Open

how to configure existing repositories in a github org? #934

sm43 opened this issue Oct 20, 2022 · 3 comments
Labels
feature New feature or request

Comments

@sm43
Copy link
Contributor

sm43 commented Oct 20, 2022

#890
with this pull req we allow user to enable auto configure new repos but how do we support configuring existing repos in the org.

few of the ways discussed in the comments
#890 (comment)

we have 2 ways now...

if auto configure is enabled then list all repos which are attached to github app.. (I guess there should be some api) and then create repository Cr for it.
or when we get event from that repo, and we don't find a any repository cr for it. we create one. (not secure but we will have to check where the event is coming from using some regex/org name)

and #890 (comment)

(about importing existing repo since this PR handles only newly created repos).
maybe having a import flag in the CLI could solve this, it will :
tkn pac import organisation org
will go over every repos in the org organisation and create a namespace/repo using a template.
this could be used as well for other git providers too,

@sm43 sm43 added the feature New feature or request label Oct 20, 2022
@sm43
Copy link
Contributor Author

sm43 commented Oct 26, 2022

@chmouel whats the priority on this?

@chmouel
Copy link
Member

chmouel commented Oct 28, 2022

maybe having this command letting do a batch import would be useful even for non auto creation,

@mpreu
Copy link

mpreu commented Apr 22, 2023

It would be nice from my perspective, if any form of batch import can be expressed in GitOps compatible form. This means, that repository CRs might be created on the filesystem as an alternative to just in-cluster. Especially since additional features on this CR like custom parameters seemed to be merged recently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Development

No branches or pull requests

3 participants