Summary
User inquires about the possibility of creating Airbyte destinations/sources with images from a private Docker repository using Terraform, referencing the airbyte_destination_custom resource and noting a lack of documentation on the subject.
Question
Hello again,
Is it possible to create destinations/sources where the image is located on private docker repository using Terraform?
Found the airbyte_destination_custom one but not too much info in the documentation. And since I cant find any documentation regarding image there I suppose it’s not what im looking for?
https://registry.terraform.io/providers/airbytehq/airbyte/latest/docs/resources/destination_custom
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.
Join the conversation on Slack
['terraform', 'airbyte_destination_custom', 'private-docker-repository', 'documentation']
hmm, or do I create the destination so it shows up as a destination and then refer to that one using the
definition_id property in the terraform resource?
If thats the case it would be nice to have the definition_id available in the GUI, but guess I’ll find it in the db
Please add 
:skin-tone-2: in this discussion and/or write a comment https://github.com/airbytehq/airbyte/issues/42990#issuecomment-2408399791
At this moment custom connector has to be added manually and then it can be used in terraform. I don’t think there is an easy way to get definition_id. Personally I get it from database, but it is also possible to use some internal endpoints /api/v1/source_definitions/list_for_workspace, /api/v1/destination_definitions/list_for_workspace
Another method is to open browser’s developer tools and update your connector to any version, then in payload you should see definition id
added some thumbs. As the latest poster said we need this to be able to fully provision resources using Terraform
hmm, or do I create the destination so it shows up as a destination and then refer to that one using the
definition_id property in the terraform resource?
If thats the case it would be nice to have the definition_id available in the GUI, but guess I’ll find it in the db
Please add :skin-tone-2: in this discussion and/or write a comment https://github.com/airbytehq/airbyte/issues/42990#issuecomment-2408399791
At this moment custom connector has to be added manually and then it can be used in terraform. I don’t think there is an easy way to get definition_id. Personally I get it from database, but it is also possible to use some internal endpoints /api/v1/source_definitions/list_for_workspace, /api/v1/destination_definitions/list_for_workspace
Another method is to open browser’s developer tools and update your connector to any version, then in payload you should see definition id
added some thumbs. As the latest poster said we need this to be able to fully provision resources using Terraform