Open Adrian-TL-KPS opened 2 months ago
Hi @Adrian-TL-KPS
I am not sure we want to make the connector part of this terraform provider, as it is a very different part of their product offering, with a separate client and all. It might thus be better off as a separate terraform provider. Conversely it looks like the same API client credentials can be used for both composable commerce and connect, so I guess commercetools themselves sees this as part of a single API.
I will discuss internally which approach to take here, but adding the resources themselves should not be too hard regardless.
Hi @Adrian-TL-KPS
Right, we will add it to this provider. However currently we have no internal usecase where we need commercetools connect, so this will be somewhere on the backlog until I can find time to pick it up.
Feel free however to create a PR implementing the features, and if you need any guidance on that let me know!
Sure, no problem. I wanted only to add the issue so that it can be planned for the future.
I'm learning go on my spare time and may try when I feel ready.
Hi labd team,
CommerceTools has a new feature called CommerceTools connect. It can be configured from their cockpit, but it would be nice to be able to manage it via terraform using your great provider.
The CommerceTools connect types that we are missing in the current version of the provider are: connector, connector stagged and deployment:
Thanks for the great work.
Cheers, Adrian