Request to package localstack

[CMCDragonkai]

https://github.com/localstack/localstack is a fully functional local AWS cloud stack. It allows you to mock AWS services and develop tests for applications that rely on AWS.

If nobody gets around to this, I may work on this later.

[mogorman]

i started a pr for this will try to get more to it so it can be merged

[stale]

Thank you for your contributions.

This has been automatically marked as stale because it has had no activity for 180 days.

If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.

Here are suggestions that might help resolve this more quickly:

1. Search for maintainers and people that previously touched the related code and @ mention them in a comment.
2. Ask on the NixOS Discourse.
3. Ask on the #nixos channel on irc.freenode.net.

[risicle]

Removing stale label as I've been looking into this more.

A few tricky things about localstack that I've discovered in researching this:

1. "localstack"'s code seems quite interwoven with the code for "localstack pro". For instance the main package localstack depends on localstack_ext, a package that exists on pypi but for which the source is not publicly hosted. You can of course download the tarball from pypi and read the source, though much of it seems to have been minified, but the largest chunk of that package seems to consist of .py.enc files - encrypted python files. I guess these get "unlocked" when you pay for "localstack pro". I think it's a bit creepy to have all this mystery code floating about and I'd be hard pressed to call this an "open source" dependency. Maybe we'd be able to just do a find . -name '*.enc' -delete in a postFixup to avoid installing this on people's machines and this would be fine, I don't know.
2. It appears to depend on a forked moto, which they host at https://github.com/whummer/moto and publish as the pypi package moto-ext https://pypi.org/project/moto-ext. The problem is that this package still retains the toplevel import name moto, and so we wouldn't be able to include this package in pythonPackages due to the "no colliding packages" policy. It would would still be possible to keep localstack as a regular application, not exposing its internal moto-ext outside the derivation.

[CMCDragonkai]

Is it possible to bring in a python dep without propagating it?

[stale]

I marked this as stale due to inactivity. → More info

[jonringer]

might be 40 months late, but I took a stab at this.