-
Notifications
You must be signed in to change notification settings - Fork 26
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 and ship github-to-sops with pip #324
Comments
https://simonwillison.net/2024/Jan/16/python-lib-pypi/ seems helpful |
https://github.com/prefix-dev/rattler-build/blob/main/examples/rich/recipe.yaml for an example of doing this with rattler-build for conda. |
I'd like to look into Willison's method |
@rjwignar awesome, thank you. I would suggest you continue work in the gitub-to-sops repo vs. here, but I'll leave this open as a tracking issue. Don't pay attention to what I've done for rattler; do what Simon says to do. The rattler build can leverage whatever you do with pip. |
We should figure out which pieces of this we can get done by 1.1 (next Friday), even if we can't get it all in by then. |
I recently made a PR that modifies Publishing to PyPI first requires filling a Pending Publisher form to use PyPI's Trusted Publishers mechanism. Here's an example form Willison filled out for one of his libraries: I haven't tried it yet, but I think I'd be able to fill out (using the |
@WangGithub0 do you want to review tarasglek/github-to-sops#3 as well, since you did something similar for the TypeScript module? |
sure, I'll do it |
@rjwignar can we close this now? |
@humphd Thanks for reminding me. |
We're using sops and GitHub to secure secrets in the repo, and @tarasglek has created a neat Python tool to make it easier to do: https://github.com/tarasglek/github-to-sops. Let's get this packaged so it can be installed with
pip
The text was updated successfully, but these errors were encountered: