Possible implementation of external studio host as a resource itself

petero-dk commented 2 weeks ago

Why would I want this: The same sanity project is used in a couple of different deployment pipelines (think staging / prod / dev) and for the Sanity project only one would be able to have the resource of the project (which i don't want) so I have linked the Sanity project as a data object in terraform.

However for my production pipeline, I would like to set the external host name as that is dependent on other resources in that pipeline.

Currently that is not possible because it is available only on the project resource.

Highlights?!?:

Is it even possible to reset the ExternalStudioHost from the sanitly go client, because of https://github.com/tessellator/go-sanity/blob/a666c794259cbd9cb4e41734c3d0ed4b36461576/sanity/projects.go#L201' if I wanted to reset it to nothing I cannot do that?

tessellator commented 1 week ago

Hi @petero-dk. Thanks for this PR! I haven't yet had a chance to take a look at this, but I plan to in the coming week. I appreciate your patience. :)

tessellator commented 1 week ago

I opened up #2 so we can put discussion about the problem itself in there decouple from the implementation in this PR.

tessellator / terraform-provider-sanity

Possible implementation of external studio host as a resource itself #1