Ben Drucker

Couple of small issues were present leading to this bug, see #67. As for the fact that the returned error is "you don't have permission" rather than "context not found,"...

Notable differences, this project has: * Tests * Context support tomtucka's adds: * An `env_vars` map in `circleci_project`, which would conflict with `circleci_environment_variable`. The docs incorrectly show this as a...

> Contexts are not yet supported via a go client which is why my project doesn't incorporate them as the Provider developer guide states that you should only use one...

Also, from #70: > When I try to apply again the resources fails because it already exists. This would suggest that retrying would not be the answer. A client is...

Context deadline exceeded is a generic Go timeout error. I take it from your comment that this is repeatable but it's not reproducible from the acceptance tests, which FWIW I...

Weird. > Is it easy enough for me to run acceptance tests to try and see if I can reproduce there as well? Yeah! There's a few required env vars...

Ok nice, an error on `GET` is always going to be retryable. A timeout error on `POST` is potentially retryable but if the underlying request actually succeeded the retry will...

If a response isn't received more or less immediately, it's unlikely to ever come. The response timeout case is pretty tough because it means a connection was successfully opened and...

Would be good to put a request to Circle about adding this to the official API. If it's not already requested on https://discuss.circleci.com you could mention there. PR welcome using...

Reminder @mrolla 🙂