After writing a connector, i created a file

airbyte-config/init/src/main/resources/config/STANDARD_SOURCE/778daa7c070c.json

with this content:

{
  "sourceId": "778daa7c070c",
  "name": "File",
  "dockerRepository": "airbyte/source-file",
  "dockerImageTag": "0.1.0",
  "documentationUrl": "<https://hub.docker.com/r/airbyte/source-file>"
}

However when i start the

docker-compose --env-file .env.dev -f docker-compose.yaml -f docker-compose.dev.yaml up

command and open the browser, i don't see my source-file in there, am i missing something?

You might need to start with

docker-compose down -v

these files are only loaded once, the first time you create the volume

it doesn't seem to do anything different...

hum

removing /tmp/dev_root fixed it

the seed data step only works the first time we run the app. In dev if you want to start from a clean slate you also need to remove the /tmp/dev_root, otherwise it doesn't get updated with the new base configurations

I had to properly come up with some kind of uuid too... which i didn't before as i just wrote down random sourceId...

yes it works now thanks!

if i change code in my python integration-connector code, how do i make sure that the new code is properly redeployed to be used when i docker-compose up? (what commands do i have to run? just

gradlew build

is not enough, right?)

(do i have to change the uuid of the files in the standard_source ?