-
Notifications
You must be signed in to change notification settings - Fork 42
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
[Package Request] - Add git-crypt #661
Comments
It is possible to build packages like these from the Fedora or Centos Stream repos as I've done here: |
+1 would like this package |
I normally like to also rely on GitHub releases if they're available but it doesn't provide enough cross-compiled versions. https://github.com/AGWA/git-crypt/releases/tag/0.7.0 Ideally, for GH releases I like to see Darwin and Linux |
I also cross-posted a request for more binaries via GitHub releases. AGWA/git-crypt#309 I'm okay obtaining binaries directly from projects when they're available. In general, I'd like to avoid compiling if the binaries are available (compiling is okay too; just more time consuming in the Docker build process). |
If you use COPR, it creates a repo that will mostly keep itself up-to-date. Ideally Amazon should add packages but I can understand that they'd want to keep the supported package number down. |
What package is missing from Amazon Linux 2023?
git-crypt is a CLI utility which is used to decrypt secrets using GPG stored within a git repo.
Is this an update to existing package or new package request?
New request because the package is missing.
Is this package available in Amazon Linux 2? If it is available via external sources such as EPEL, please specify.
Unknown, I only care about Amazon Linux 2023 and haven't looked into Amazon Linux 2.
Any additional information you'd like to include. (use-cases, etc)
If a GPG private key is available you should be able to run
git crypt unlock
to decrypt secret files from gitattributes.Current (undesirable) workaround is:
We have both Graviton and AMD64 infra so this solution is fragile since it relies on a source that is currently uncontrolled.
Ideally, we should just be able to run the following on both Graviton and AMD64 instances.
The text was updated successfully, but these errors were encountered: