Open zeke opened 6 years ago
ping @benschwarz
Trello Power-Ups don't actually allow privileged credential storage, just shared and private "visibility", but perhaps worth knowing about: https://developers.trello.com/reference/#get-set-custom-data
I would love if a GitHub App could:
reminder:<2017-04-20
)Is this still causing friction? If so, please comment with any updates or addition details.
oh boy it does this cause friction 😽
💡 What about storing encrypted values in .github/config.yml
that only a probot installation can decrypt?
Like Travis Encryption keys.
What about storing encrypted values in .github/config.yml that only a probot installation can decrypt?
Adding the encrypted key to the file would be the tough part - you'd need some kind of UI to input the unencrypted key, then maybe the app could open a PR adding it?
sounds like something I’d love to have built-in into Probot or an extension
@zeke, @JasonEtco - Encrypted values in .github/config.yml
sounds like a good first step.
Although if the app had to request permissions for opening PRs to add it (but otherwise that app didn't need those permissions, it'd look a bit fishy to users).
Forgot to say, this is definitely something that causes friction. I could see a lot more applications successfully using probot if there were a github-side encryption service or something of that nature.
Here's an experiment with using the private key to encrypt secrets: https://gist.github.com/bkeepers/c52ab6854cd549457561e75dbad93744 (use at your own risk)
GistAn experiment using a RSA private key to encrypt/decrypt secrets.
It seems the initial setup could be done by redirecting during installation, but how would the config key be updated by users after that?
Is this still causing friction? If so, please comment with any updates or addition details.
Hi @stale. Yeah this issue is still relevant.
Is this still causing friction? If so, please comment with any updates or addition details.
a lot.
I wonder why it got staled when the issue has a "pinned" label and stale is configured to ignore issues that have it? https://github.com/probot/.github/blob/da58fd987250c4d97307d740c632221d3d5b37db/.github/stale.yml#L8-L10
GitHubOrg-wide settings. Contribute to probot/.github development by creating an account on GitHub.
Is this still causing friction? If so, please comment with any updates or addition details.
It’s supported for actions, but major friction for apps
For myself, I'm running my Probot out of a kube cluster, so I stored all of my secret bits in a kubernetes secret - but only because there wasn't any better way to do it. Would be kinda cool to see this move forward.
I still hope that secrets will be made available to apps similar to how they are made available to actions :) Maybe in a similar way as the single file access, where you have to define explicitly which secrets the app gets access to. We will update this issue if there are any news on that
Is this still causing friction? If so, please comment with any updates or addition details.
Is this still causing friction? If so, please comment with any updates or addition details.
Is there any update regarding this issue?
GitHub Secrets are still only available in GitHub Actions, but not to GitHub Apps.
cc @jovel
Migrated from https://github.com/probot/ideas/issues/69