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

Add SSH support for age #1692

Merged
merged 8 commits into from
Feb 20, 2025
Merged

Add SSH support for age #1692

merged 8 commits into from
Feb 20, 2025

Conversation

haoqixu
Copy link
Contributor

@haoqixu haoqixu commented Dec 1, 2024

Continues #1134.

Closes #1134
Closes #1496
Fixes #692

@haoqixu
Copy link
Contributor Author

haoqixu commented Dec 1, 2024

This PR rebases #1134 and includes _FILE in the environment variable according to the suggestion in #1134 (comment), but uses SopsAgeSshPrivateKeyFileEnv instead of SopsAgeSshPrivateKeyEnvFile to stay aligned with SopsAgeKeyFileEnv.

@haoqixu haoqixu marked this pull request as draft December 1, 2024 21:48
@haoqixu haoqixu marked this pull request as ready for review December 1, 2024 21:57
Copy link
Contributor

@felixfontein felixfontein left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your contribution, and sorry it took so long to review it...

@haoqixu haoqixu force-pushed the age-ssh branch 2 times, most recently from 1af2314 to 714f23d Compare January 2, 2025 08:14
Copy link
Contributor

@felixfontein felixfontein left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, up to two details in go.mod and the open discussions on the Code scanning warnings.

@brianmcgee
Copy link
Contributor

It looks like this PR is ready to roll once those codeql warnings are dismissed. Am I right, or is there anything else needing done?

@haoqixu
Copy link
Contributor Author

haoqixu commented Feb 7, 2025

It looks like this PR is ready to roll once those codeql warnings are dismissed. Am I right, or is there anything else needing done?

yes, I think so. 🤔

@felixfontein
Copy link
Contributor

@haoqixu can you rebase the PR and integrate getsops/docs#9 into README.rst in this repository? (README.rst is the current source of truth for SOPS documentation, not the docs repo.)

@haoqixu
Copy link
Contributor Author

haoqixu commented Feb 19, 2025

@haoqixu can you rebase the PR and integrate getsops/docs#9 into README.rst in this repository? (README.rst is the current source of truth for SOPS documentation, not the docs repo.)

No problem. Done.

Copy link
Contributor

@felixfontein felixfontein left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Besides that, LGTM.

@felixfontein
Copy link
Contributor

(I also dismissed the CodeQL warnings.)

Co-authored-by: Felix Fontein <[email protected]>
Signed-off-by: xu0o0 <[email protected]>
@felixfontein felixfontein merged commit 0cea11f into getsops:main Feb 20, 2025
16 checks passed
@felixfontein
Copy link
Contributor

@mstrangfeld @haoqixu thank you very much for your work on this, and thanks again @iamd3vil for getting it started in #898!
Also thanks to everyone involved in providing feedback and testing #898, #1134, and this PR!

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

Successfully merging this pull request may close these issues.

Adding support for ssh keys for encryption.
4 participants