search

opentofu / registry-alpha

Home of the official OpenTofu provider and module registry
Apache License 2.0
64 stars 13 forks source link

Make the resource names user provided #75

Open jamengual opened 1 year ago

jamengual commented 1 year ago

Hi.

I noticed that resource names are hardcoded and will not match naming conventions for a lot of people, I was wondering, are there plans to make this more flexible?

https://github.com/opentofu/registry/blob/main/iam.tf#L29

or is this expected to be an example on how to run the registry? if that is the case, the lambda code maybe should have its own repo so that people can use their own way to deploy the API gateway and lambda but they can still pull the lambda code from a repo that has it's own SDLC.

Thanks.

Yantrio commented 1 year ago

Hi @jamengual! thanks for raising this.

Right now this code is intended to be temporary and to get us off the ground and we did not take into consideration other people running this so soon!

Once things are a little more settled in the near future we can look at making this a bit easier to consume by other people. I love the idea of people being able to run just the lambda+dynamodb setup along with their own api gateway so they can bring along their own caching if they wish. We have also discussed internally about making the route53 part seperate so we can consume the apigateway with it's caching directly without the need to have a domain configured to get going.

We've recently done a large refactor of the golang code, and I'm sure that we will be doing one for the terraform too to make sure it's clean and easy for people to contribute to and we should 100% take your point into consideration!