* Revert "Revert "Add dependencies to docker-compose (#19257)" (#19306)"
This reverts commit b16f28fd4d.
* Bump docker-compose version
* test
* Revert "test"
This reverts commit c3b28c9ec3.
* Bump docker compose version to 3.8
* test
* test
* Use a newer docker for platform build
* test
* Use docker compose v2
* Update docker for frontend e2e
* Use docker compose v2 for e2e tests
* Update tools to use docker compose v2
* Update more docker compose references to v2
* Update docker compose usage in docs
* Update deploying airbyte docs
* Fix permission
* Case insensistive check
* Add extra mention for docker compose in upgrading airbyte
* Improve upgrade docker note
Define logic in root build.gradle to create a task in each subproject if the subproject contains dockerImageName in the gradle.properties file.
Some caveats:
- We also define a copyGeneratedTar task that is applied to all subprojects with the dockerImageName property.
- This does not need to be used in each subproject. We leave it up to each subproject to define what task is depends on since some projects have more custom copy logic.
* add documentation for running the dev image of a connector
* Apply suggestions from code review
Co-authored-by: Augustin <augustin.lafanechere@gmail.com>
* remove unwanted directory from PR
Co-authored-by: Augustin <augustin.lafanechere@gmail.com>
* `LOG_CONNECTOR_MESSAGES` to enable logging of all messages seen by the worker in a sync
* also log initial state
* linting
* getState 2x for to match input file
* use `Jsons.serialize` utility
* add note to `developing-locally`
* fix bad merge
* improve doc for contributing locally
- the format command for an individual connector is airbytePythonFormat
- provide examples for the format commands
* add `./gradlew format` for java connectors
Clean up and add better guidelines on how to use the Java catalogs we recently added.
Took the chance to move existing documentation to improve reading flow.
* Dockerfile to 3.9
* Python version
* More python updates
* 3.9 on GitHub actions and lint updates
* Test out 3.9.11 on GitHub actions
* install python with an action
* formatting: newline
* Also has python code
* only check first level for changed modules
Previous example (source-google-search-console/credentials)
* Test failure: there is no logger.trace
* Add script to setup venv for a connector
* new line
* echo
* Add missing requirements file
* Add script to add venvs to intellij
* script to install venv
* Update
* This should be easier to use
* Better default
* Add unit tests
* add install venv option flag
* remove references to my own own home directory
* Call tools/bin/setup_connector_venv.sh
* Skip module if it already exists in the jdk table
* update
* Set right test name
* better interface
* update
* rename flag
* move to a function
* fix variable name
* derp
* Use real path
* Update setup instructions
* update instructions
* Instructions to both install the venv and update intellij
* update link
* Add command to install venv for all connectors
* <>
* newline
* Revert "Revert "Build OSS branch for deploying to Cloud env (#11474)""
This reverts commit 55e3c1e051.
* add action to get dev branch tag to OSS project instead of doing it in cloud
* remove dev branch version action, going to do this in cloud afterall
* add VERSION buildArg to Dockerfiles, default to current airbyte version but overwritable
* use VERSION env var consistently as Dockerfile buildArg, jar version, and tag
pass version and image_tag into docker build task function
* add github action for building and pushing an OSS branch for Cloud to consume
* allow AirbyteVersion to validate versions containing 'oss-branch' prefix
* change oss-branch prefix to dev for branch-based versions
* better action name
* add docker-compose-cloud.build.yaml to define minimum set of cloud images that are pushed by oss branch action
* update local dev docs to describe optional usage of VERSION env var
* make branch_version_tag input optional, if not provided, generates dev-<commit_hash>
* fix typo
* fix missed merge conflict
* update docker docs
* update integrationRunner isDev check
1) Remove requirement for local Postgres, because it is no longer needed
2) Fix bash code snippet for running acceptance tests (remove the line that starts Airbyte)
3) Document how to use USE_EXTERNAL_DEPLOYMENT flag
Macs with M1 chip can run Airbyte only in dev mode right now, so to make it clear, I added a note about it and moved the hint about M1 chips to the top of the section.
