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
aws-env: init at 0.4 #47414
aws-env: init at 0.4 #47414
Conversation
@GrahamcOfBorg build aws-env @ento I don't believe it's a hard requirement that new packages absolutely must have a maintainer, but it certainly is preferable by a large margin, so that people at least have someone to ping on github to ask for reviews of version bumps etc. |
No attempt on x86_64-linux (full log) The following builds were skipped because they don't evaluate on x86_64-linux: aws-env Partial log (click to expand)
|
No attempt on x86_64-darwin (full log) The following builds were skipped because they don't evaluate on x86_64-darwin: aws-env Partial log (click to expand)
|
No attempt on aarch64-linux (full log) The following builds were skipped because they don't evaluate on aarch64-linux: aws-env Partial log (click to expand)
|
Ah, this needs an entry in |
D'oh, added to all-packages.nix in 6e8a5b0. I can squash the commits if that's preferable. re: maintainer - got it. Is the ping more for Nix expertise or for knowledge of the package content itself? |
@ento I'd say in this case where it's a relative simple package, the question that people will mostly be aiming at the maintainer is probably "hey, I updated this package, is that OK?" And yes please, squash 'em. :) |
@GrahamcOfBorg build aws-env |
Success on aarch64-linux (full log) Attempted: aws-env Partial log (click to expand)
|
Success on x86_64-darwin (full log) Attempted: aws-env Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: aws-env Partial log (click to expand)
|
They've been squashed.
Being a mere user of aws-env, I'll only be able to say "I guess?" and double-check any open issues for aws-env at most. So I'll cc @orfin for any interest in having your name listed as a maintainer / point of contact for aws-env in Nix (if there's interest, we can update the package metadata in a separate PR), and ask the good reviewer(s) of nixpkgs to consider it a non-blocker to have no maintainer listed for this package for now. |
@ento Alright, but I'd feel bad adding a package with no maintainer, so can you please add me ( |
@srhb Thank you, much appreciated. I've updated |
Thank you. :) |
Motivation for this change
This PR adds aws-env, a useful tool for pulling environment-specific variables from AWS Systems Manager Parameter Store.
The contributing guide requires that
meta.maintainers
be set; I'm not really good at being a maintainer - what'd be the protocol in that case?Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)