* sweep all scheduler application code and new-scheduler conditional logic
* remove airbyte-scheduler from deployments and docs
* format
* remove 'v2' from github actions
* add back scheduler in delete deployment command
* remove scheduler parameters from helm chart values
* add back job cleaner + test and add comment
* remove now-unused env vars from code and docs
* format
* remove feature flags from web backend connection handler as it is no longer needed
* remove feature flags from config api as it is now longer needed
* remove feature flags input from config api test
* format + shorter url
* remove scheduler parameters from helm chart readme
## What
Part 2 of https://github.com/airbytehq/airbyte/pull/13122.
Follow up to #13476 .
Explanation for what is happening:
Identically named subprojects have the following issues:
* publishing as is leads to classpath confusion when the jars with the same names are placed in the Java distribution. This leads to NoClassDefFound errors on runtime.
* deconflicting the jar names without changing directory names leads to dependency errors as the OSS jar pom files are generated using project dependencies (suggesting a dependency a sibling subproject in the same repo) that use subprojects group and name as a reference. This means the generated jars look for Jars that do not exists (as their names have been changed) and cannot compile.
* the workaround to changing a subproject's name involves resetting the subproject's name in the settings.gradle and depending on the new name in each build.gradle. This increases configuration burden and decreases the ease of reading, since one will have to check the settings.gradle to know what the right subproject name is. See https://github.com/gradle/gradle/issues/847 for more info.
* given that Gradle itself doesn't have support for identically named subprojects (see the linked issue), the simplest solution is to not allow duplicated directories. I've only renamed conflicting directories here to keep things simple. I will create a follow up issues to enforce non-identical subproject names in our builds.
* Rename airbyte-config:models to airbyte-config:config-models.
* Rename airbyte-config:persistence to airbyte-config:config-persistence.
* Rename docker secrets and parameterize docker user
* Apply suggestions from code review
Co-authored-by: Pedro S. Lopez <pedroslopez@me.com>
Co-authored-by: Pedro S. Lopez <pedroslopez@me.com>
* Show summary on action results for failed test
* Write title and steps to log
* Log test
* Remove debugging
* Support python and java output
* Extra line break
* kill containers using volumes on shutdown in acceptance test scripts
* apply change to octavia integration tests as well
* escape inner command to make it be executed at the right time
* added multiarch image publishing/modified dockerfiles
* added new ami
* changed version to test
* rollback version
* check version test
* env vars temp fix
* apt-utils error fix
* disabled failed test
* remove excluded tests
* Excluded :airbyte-db:lib:test
* Excluded :airbyte-db:lib:test
* static jdk version for test
* ok test
* ok test
* ok test
* test vars
* quemu issue fix
* Returned version vars
* Scripts update
* Version vars change
* Comment fix
* Added comments, minor changes and comments in dockerfiles
* Uncomment line to push images
* Check for ssh github repo
because assumptions mostly.
more clear fail messages for an unsupported workflow
also removes the pipeline which now is redundant with local workflow
* WIP1
* working test
* More clear git test
* less weird characters for grep
* remove verbose for excho
* WIP
* WIP2
* WIP3
* Remove comment/better comments
* Remote deployment updates
* Adds GH user for yarn deploy
* WIP 6
* WIP7
* WIP8
* WIP 10
* Working easy from home
not so much in the cloud
* Addreses another docs build error
* Remove two typos
* Adds a test pattern
* Another stab
* More test
* Removing pipeline until more testing
docusaurus deploy isn't into automation
* Adds deploy docusaurus command
(won't work yet. commit for testing)
not force pushing
* Adds GH token workflow for GH actions
* Small comment changes
* Adds branch name to push
* adds gh switch
* Commit for clear dir for testing
* Addresses comments by adding comments
* 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
* Brings pairity for doc checks from cloud
* WIP Sidebar config
It's sketchy JSON let's commit before we break i
* MVP sidebars
summary.md is no longer functional
it's higherarchy was translated into sidebar.js
as a JSON format that docusaurus likes
* Removes another unused readme
* Use shell hacks to find valid PAT
if rate limit exceeded try another key
* Use tim's version of the ec2 runner
this is a weird solution with weird limitations. should address the short term pain (march 2022)
* Record e2e tests to cypress dashboard
* Make env variable accessible in script
* Improve e2e_test script
* Properly wait for server to be ready
* Isolate test suites better
* More test isolation
* Revert baseUrl for development
