I'm creating webservices with linked environment groups. When i do the first terraform apply the service creation fails because the environment link is created only after the webservice is created (because it needs the service id) but the webservice creation waits for the first deployment to succeed (which obviously fails because it's missing the linked environment variables).
A subsequent terraform apply always tries to re-create the service (because it's marked as tainted after the first failure) so i'm basically stuck there.
I can mitigate this by manually terraform state rm the service and re-import it with terraform import (because it's created successfully on render). Then another terraform apply also creates the environment link which allows for successful deployments. But i guess that's not how it's supposed to work :)
I'd suggest to not wait for deployment results when creating a webservice.
Thanks for the report @extronics. v0.2.0 of the provider no longer waits for a successful deploy by default when creating services, which should prevent this issue.
I'm creating webservices with linked environment groups. When i do the first
terraform apply
the service creation fails because the environment link is created only after the webservice is created (because it needs the service id) but the webservice creation waits for the first deployment to succeed (which obviously fails because it's missing the linked environment variables).A subsequent
terraform apply
always tries to re-create the service (because it's marked as tainted after the first failure) so i'm basically stuck there.I can mitigate this by manually
terraform state rm
the service and re-import it withterraform import
(because it's created successfully on render). Then anotherterraform apply
also creates the environment link which allows for successful deployments. But i guess that's not how it's supposed to work :)I'd suggest to not wait for deployment results when creating a webservice.