Open willi-mueller opened 10 months ago
The problem is the specification of the workspace_id in the variable.
When I remove the default value and paste the workspace_id without the quotes upon Terraform prompting it works!
It seems that this problem is due to a race condition and waiting for the user input prevents it in most but not all cases for me. I'll update the issue later and elaborate on how to reproduce it.
Hi, is there any movement in this at all. It would be super nice if we could all be able to codify all the sources. destination and connections.
@willi-mueller sorry this has been so frustrating - could you try removing definition_id
and seeing if that works? I'm suspicious that the error message you're seeing is misleading about the workspace not existing
The provider does not like this. The argument "definition_id" is required, but no definition was found.
Thanks for testing that @antonio-one - will circle back with the team
I am running into the same problem except I'm using an S3 source/destination. Same workaround works for me too (leaving value blank and populating the value in after terraform runs. I also tried this to no avail:
echo <workspace_id> | terraform plan
I was able to workaround this further by using:
variable "airbyte_workspace_id" {
type = string
default = "MY_ID"
}
data "airbyte_workspace" "main" {
workspace_id = var.airbyte_workspace_id
}
And then use data.airbyte_workspace.main.workspace_id
for the source/destination.
I tried to use this Airbyte Terraform provider to manage my open-source Airbyte installation.
However, when I try to add sources or resources then I always get the error that a resource cannot be found for my workspace.
I would appreciate very much your help in getting this working.
Example:
However, the API lists this very workspace:
Returns:
Environment
Tested on Airbyte OSS versions: 0.50.33 and 0.50.34 Provider version: 0.3.5
Airbyte is running on GPC behind an IAM proxy. I have port-forwarding to access the API and can successfully connect to the UI as well as make API calls as demonstrated.
How to reproduce
However, this is exactly the workspace ID that I see in both my web-browser as well as in the API response as shown above
Additional trials
I tried also the MySQL source as well as the BigQuery destination:
However, it results in the same error:
Then, I thought that maybe if I import or create the workspace using Terraform it will work. However, same error:
Error:
Again, the API lists it:
What if I give the workspace's name instead of ID?
Error:
What if I import the existing workspace?
Trying to reference the imported workspace:
Then,
terraform apply
fails, but this seems to be a different problem:I would be very glad if you could take a look at this issue and help me find the problem so that I can create sources, destinations, and connections in my workspace.
Thank you!