-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Fix concurrency issues with kube config against same cluster #328
Conversation
We are reviewing PR and will be part of next week terraform provider release |
@ocofaigh we reviewed the PR its creating a new folder for each action...Lets say if user run terraform plan or apply multiple times then it will have its own directory created ..This way the folder structures gets added in each run and doesn't get cleaned up |
Instead of generating a new folder I think the better approcah is to add mutex (terraform mutex) on datasource something similar where we have lock on cluster id so that the provider executes the datasources serially |
@hkantare This is intended behaviour, otherwise concurrent data lookups on the same cluster will fail. What seems to happen with the current behaviour is:
When this process happens concurrently, you get the error: I guess another approach could be to add a lock on that process so it cannot be executed concurrently? |
I think we will go with another approcah to add the mutex from Terraform level
|
we are looking in above aproach |
No need for this PR anymore - it can be closed since the fix is in IBM-Cloud/terraform-provider-ibm#3264 which is in v1.35.0 |
closing the PR |
Related to IBM-Cloud/terraform-provider-ibm#2806