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

Is there a way to use Github App Access Token with git sync? #450

Closed
sfc-gh-cfraleigh opened this issue Nov 1, 2021 · 7 comments
Closed

Comments

@sfc-gh-cfraleigh
Copy link

We have some security concerns with using ssh and/or personal access token to authenticate git-sync with github. Is there a way we can auth using a github app?

@thockin
Copy link
Member

thockin commented Nov 2, 2021

I have no notion of how that would work. I'm not inherently against it, but I'd need someone (you?) to detail how exactly it would work. How would you configure git to do this?

@yan-hic
Copy link

yan-hic commented Nov 25, 2021

https://docs.github.com/en/developers/overview/managing-deploy-keys#server-to-server-tokens describes the steps to setup and authenticate with a GitHub App.
However, if anyone is concerned about using personal SSH keys, look at Deploy keys instead, in the same webpage/link

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 23, 2022
@thockin thockin removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 23, 2022
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 24, 2022
@thockin thockin removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 24, 2022
@thockin thockin closed this as completed Aug 20, 2022
@joebowbeer
Copy link

/remove-lifecycle stale

@joebowbeer
Copy link

@thockin I'm looking for this as well.

This was not completed, right? That is, there is no way to auth with a GitHub App? (e.g., like ArgoCD does)

If not, should I reopen this or create a new issue?

@thockin
Copy link
Member

thockin commented Jul 17, 2023

It aged out. I don't really know enough about github apps to know what this would mean. I am not against it in principle, I just haven't any idea how to do what OP wanted. Happy to discuss if someone can bring information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants