Add Terraform directory with small OpenSearch cluster for testing

acm19 / aws-request-signing-apache-interceptor

https://acm19.github.io/aws-request-signing-apache-interceptor/

Apache License 2.0

16 stars 6 forks source link

Add Terraform directory with small OpenSearch cluster for testing #73

Closed acm19 closed 2 years ago

acm19 commented 2 years ago

Add a infra directory with a Terraform project to run a small cluster for testing purposes by the contributors. Easy to setup and tear down.

dblock commented 2 years ago

Or maybe CDK?

acm19 commented 2 years ago

Good point. The way I see it in this context:

Advantages of going TF:

Drift detection (specially useful for testing or long lived test projects).
Speed, calling API without CFN overhead.
Declarative.

Advantages of CDK:

No need for backend.

I'm happy to go the CDK way for idividual collaborators cluster, I wouldn't even mind CFN directly, because of no backend needed. If at some point we need a long lived common cluster then I'd def chose Terraform, specially because of the drift detection.

dblock commented 2 years ago

Since I am not writing it, I only have opinions ;)

acm19 commented 2 years ago

Potential user are important ;)

dblock commented 2 years ago

Related, are you thinking of launching a new OpenSearch cluster in AWS on demand for integration tests and then delete it? Those clusters aren't that fast to come up. But maybe it's sufficient to run test on anything merged onto master even if that's slow ... there's no such thing as "start/shutdown cluster" AFAIK, it's create/delete. Also free tier gives free usage of up to 750 hours per month of a t2.small.search I believe.

acm19 commented 2 years ago

Cluster are slow to create and tear down. I'm planning to make it easy for someone that need to work on a bug or feature to easily spin it up and tear it down for development. Free tier for OpenSearch is for 12 months only.