You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I love the rancher provider that was added in GH-9173. My issue is that the rancher provider for me frequently but not always has a timeout. Obviously this is dependent on my environment, but I feel like the timeout should be configurable in some way. The underlying rancher go client does have a timeout setting, but I'd need to find a way to fit that in. I wanted to submit a pull request against this, but I don't yet know how to best tackle. The only choices I can see are either through an environment variable setting or an additional setting on the provider. If either seems acceptable, I'll send in a pull
Thanks,
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 15, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform Version
v0.8.6
Affected Resource(s)
rancher_stack
I love the rancher provider that was added in GH-9173. My issue is that the rancher provider for me frequently but not always has a timeout. Obviously this is dependent on my environment, but I feel like the timeout should be configurable in some way. The underlying rancher go client does have a timeout setting, but I'd need to find a way to fit that in. I wanted to submit a pull request against this, but I don't yet know how to best tackle. The only choices I can see are either through an environment variable setting or an additional setting on the provider. If either seems acceptable, I'll send in a pull
Thanks,
The text was updated successfully, but these errors were encountered: