Open demeyerthom opened 1 month ago
Hi @dotansimha any additional information I can provide to get this on the road? We are currently implementing this through a workaround way in terraform, but I would much rather have a dedicated terraform provider ;)
Hi all.
First of all thanks a lot for this cool application!
We are looking to pivot away from Apollo studio as a registry for our clients, and Graphql Hive is a good contender to make this switch because of pricing and feature set.
Part of our current setup is that we manage the subgraphs as resources in Terraform. See the Apollo Studio Terraform provider we built for this purpose: https://registry.terraform.io/providers/labd/apollostudio/latest/docs. In this way we can keep the publishing of graphs as closely to our deployments as possible
In essence I would like to be able to continue using this pattern if we would make the switch to Hive. I saw in the CLI that it makes calls to the Graphql Gateway to run its actions, this would also be perfect for my usecase. However I think the calls made by the CLI are being limited by checking the queries against a list of persisted documents, as I am unable to call the Gateway with my own queries.
Is there a way for me to call the gateway with my own queries? These can be based on the same calls as the CLI, but I am worried that any change in the CLI would also impact the provider. I would be happy to create the provider, but need some guidance on how to connect with the graphql gateway.
Thanks in advance!