-
Notifications
You must be signed in to change notification settings - Fork 13
support for aws / local config initialisation #21
Comments
@fommil You can configure all Kinesis settings/endpoints in the |
yeah, but not publicly. |
->>> slack :) |
This issue confused me initially because I thought that the library couldn't support local kinesis streams. I've been able to successfully implement LocalStack + this library; just need to consider the following:
|
Thanks @etspaceman - I know @fommil used Kinesalite directly to ease creation of streams on startup. I plan to look into this more and add a testkit module to the library |
@etspaceman Thanks for posting this bit, it was blocking us for a while! 😄
|
I do like how consistent Amazon is with the KPL and KCL libraries ;) |
Happy to help @j-potts! I had to dig through some KCL/KPL issues to really find what was going wrong. Was bugging me for days. |
@markglh just an FYI - Kinesisalite is actually what LocalStack uses so this should work for that too. |
Yeah it wraps it - it's a nice entrypoint for all the different AWS services. Hopefully we can get it working using that as it'll make working across services in docker much cleaner. I'm not sure of the exact details as I'm yet to dig into it and compare what @fommil did with this: |
I've actually got mine working in docker today, across containers, using the localstack/localstack image + their awscli-local solution. Would be happy to post a Gist! Mine uses --net host though, so if you are wanting to use the docker networking it'll need some tweaks like link/port references. |
Ooh yeah that would be awesome! |
Here's the gist. Use either docker-compose.yml or create_localstack_container.sh, then run create_kinesis_stream.sh. See the local.env.template for a .env template on your setup. I also included a reference.conf file uses the same environment variables. Our app has startup scripts that export the .env file into environment variables for either docker or a local run, which makes its way into the reference.conf. https://gist.github.com/etspaceman/137f7f540af32bf106873813c830a699 You can get pretty fancy with the docker compose setup. If you tie in the create kinesis stream to the container startup command, you can chain the localstack creation along with your service. Be sure to install awscli-local via PIP: https://github.com/localstack/awscli-local |
I would want to add that if you don't want avoid verify-ssl in you local env you could add a kinesalite-server-crt-pem file and config your aws profile with this line
also you should add a new entry host
so instead @fommil suggestion
you could create a stream
certificate could be found here: |
Implemented in: #34 |
AWS seems to use magic to provide the host/port and creds, whereas using a local docker mock of kinesis requires other information. It would be good if all this setup was abstracted away such that evil
branches are minimised / localised to this project and tested in the field with the long hard stick of production support.
That's a guaranteed bug, right there.
The text was updated successfully, but these errors were encountered: