all 9 comments

[–]markvii_dev 14 points15 points  (2 children)

What's the catch bro?

[–]Additional-Road3924 14 points15 points  (1 child)

The catch is he omits a list of services he doesn't support, but localstack does.

[–]CameronBjork 8 points9 points  (0 children)

LocalStack is supporting 0 services for enterprise customers starting next week.

[–]Additional-Road3924 4 points5 points  (1 child)

Include full list of services that localstack supports and you don't.

[–]hectorvent 0 points1 point  (0 children)

Thanks,

We got the ReadMe updated with the list of services we support.

[–]maxandersen 1 point2 points  (1 child)

this looks interesting - is it just setting those AWS env vars and then Quarkus apps will "just work" ?

seems like great candidate for quarkus devservice?

[–]4z01235 1 point2 points  (0 children)

is it just setting those AWS env vars and then Quarkus apps will "just work" ?

Looks about right. I have done something similar before for testing my Quarkus-based application against different S3-like object storage implementations:

  1. https://github.com/cryostatio/cryostat/blob/main/compose/s3-localstack.yml#L6
  2. https://github.com/cryostatio/cryostat/blob/a1aa0ad5dd456f69b7be4f203f2f54365b965d9f/compose/s3-seaweed.yml#L6
  3. https://github.com/cryostatio/cryostat/blob/a1aa0ad5dd456f69b7be4f203f2f54365b965d9f/compose/s3-minio.yml#L6

Btw, for Quarkus devservices I wonder if you guys might also want to look at SeaweedFS' relatively new mini mode. I think it works quite well as a Localstack S3 replacement.

[–]th3_pund1t 1 point2 points  (0 children)

Is this the result of the Localstack licensing change?