Multiple Keys for Different Repos #5193
-
|
I am having a hard time understanding a concept here. I have my core flux code in my personal repository. (It manages many clusters in my network) But I also own an organization that I need to deploy from. The fine grained tokens do not allow me to cross organizations. So flux will not be able to see the repo that is in my organization. The repo in my organization is an application. And I have some manifests that will deploy that code that I want flux to be able to pickup changes on. So the CI/CD for the application just updates the deployment with the new image tag. I am not sure how to add the organization specific PAT to flux that was bootstrapped to the core repo, and then specify that PAT for the application repo in my core flux code. I looked at multiple tenets and I don't think that is what I want. Also I did a search in the discussions, but I did not find one that exactly matches my question, so if it is a duplicate, I do apologize. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
This is what the Get Started guide shows but for a public repo. In your case you also need to generate a secret with a PAT from a user in that org and set it in the To generate the secret: flux -n flux-system create secret git my-org-token \
--url=/~https://github.com/org/repo --username=flux --password=$GITHUB_ORG_PAT |
Beta Was this translation helpful? Give feedback.
-
|
Ooooooh okay. Thank you. I was missing the spec. I appreciate it! |
Beta Was this translation helpful? Give feedback.
This is what the Get Started guide shows but for a public repo. In your case you also need to generate a secret with a PAT from a user in that org and set it in the
GitRepository.spec.secretRef.To generate the secret:
flux -n flux-system create secret git my-org-token \ --url=/~https://github.com/org/repo --username=flux --password=$GITHUB_ORG_PAT