Sunny Rekhi
12/28/2022, 5:33 PMdocker-compose up. I even modified other connector names in source_definitions.yaml to see if the changes show up in the UI, I'm not seeing the UI source list change at all.
I thought running VERSION=dev docker-compose up would solve the problem, but then I get this error:
terminal$ VERSION=dev docker-compose up
WARNING: The RUN_DATABASE_MIGRATION_ON_STARTUP variable is not set. Defaulting to a blank string.
WARNING: The DEPLOYMENT_MODE variable is not set. Defaulting to a blank string.
WARNING: The LOG_CONNECTOR_MESSAGES variable is not set. Defaulting to a blank string.
WARNING: The SHOULD_RUN_NOTIFY_WORKFLOW variable is not set. Defaulting to a blank string.
WARNING: The SECRET_PERSISTENCE variable is not set. Defaulting to a blank string.
WARNING: The JOB_ERROR_REPORTING_SENTRY_DSN variable is not set. Defaulting to a blank string.
WARNING: The NEW_SCHEDULER variable is not set. Defaulting to a blank string.
WARNING: The WORKER_ENVIRONMENT variable is not set. Defaulting to a blank string.
WARNING: The GITHUB_STORE_BRANCH variable is not set. Defaulting to a blank string.
WARNING: The REMOTE_CONNECTOR_CATALOG_URL variable is not set. Defaulting to a blank string.
WARNING: The TEMPORAL_HISTORY_RETENTION_IN_DAYS variable is not set. Defaulting to a blank string.
WARNING: The UPDATE_DEFINITIONS_CRON_ENABLED variable is not set. Defaulting to a blank string.
Pulling bootloader (airbyte/bootloader:dev)...
ERROR: manifest for airbyte/bootloader:dev not found: manifest unknown: manifest unknown
Any idea how to fix? Am running on Mac M1. Regular docker-compose up works fine
The docs say:
Note that modifications to source_definitions.yaml will only be picked-up the first time you start Airbyte, or when you upgrade Airbyte, or if you entirely wipe our your instance of Airbyte and start from scratch.I've shut down the docker containers, and git pulled the latest code to force an update. That didn't work.
Marcos Marx (Airbyte)
12/28/2022, 6:11 PM