* init
* bad copy/paste
* move to top level
* Revert "move to top level"
This reverts commit aca3534d38.
* attempt to wire up connector builder frontend to server
* copy from octaviacli
* fix connection to builder server
* update
* delete
* Update
* delete python-version
* Revert "delete python-version"
This reverts commit f9258a7755.
* setup python
* install python
* rename
* kube stuff
* Install python
* missing kube file
* rename
* Update files
* Update bumpversion
* install python
* try with different entrypoint
* rename container
* point to docker-compose.yaml file
* derp
* copy acceptance_test.sh
* copy from acceptance tests
* delete cruft
* update
* remove application env
* reset
* reset to master
* update
* skip comprehensive incremental tests
* Revert "skip comprehensive incremental tests"
This reverts commit 9cee657596.
* reset to master
* remove cruft
* delete superfluous steps
* update port to 8003
* reset to master
* Update publish docker
* move openapi spec to airbyte-connector-builder
* point to openapi spec
* dont expose the connector builder to localhost
* reset FE components to master
* Don't deploy the connector-builder
* Revert "Don't deploy the connector-builder"
This reverts commit 3d157494cf.
* Revert "Revert "Don't deploy the connector-builder""
This reverts commit beac3d48f0.
* comment out more things related to connector builder server
* more attempts at removing the connector builder
* comment out more things
* Apply suggestions from code review
Co-authored-by: Lake Mossman <lake@airbyte.io>
* Update airbyte-webapp/src/config/configProviders.ts
Co-authored-by: Lake Mossman <lake@airbyte.io>
* update
* rename
* indent
* Revert "move openapi spec to airbyte-connector-builder"
This reverts commit 57dda04723.
* Revert "rename"
This reverts commit b2d802b8fa.
* Revert "Revert "rename""
This reverts commit 91db24fd4a.
* point to wrong file in case it fixes the build
* point to right openapi file
* Revert "Revert "move openapi spec to airbyte-connector-builder""
This reverts commit e46a837454.
* point to moved file
* fix path
* Update from master
* newline
* Add failing test
* Revert "Add failing test"
This reverts commit ed9fea09b5.
* comment
* update commented requires
* Add a comment
* 2022
* rename to connector-builder-server
* typo
Co-authored-by: lmossman <lake@airbyte.io>
it seems github APIs want us to use longer shas in some cases where a
7 character short sha is still entirely valid
So just set the minimum short sha length to 10
* Use more specific variable name
* Write affected sources and destinations to files
* Use Markdown template to format results
* Update workflow to edit existing comment instead of making a new one
* Check whether changed_files.txt is empty before proceeding
* move template to .github/
* Use different quotes for true
* Move logic about continuing back to after dependency report because of ignores
* Use correct filename in conditional
* Use if to avoid early exit
* Create folder for comment templates and use constant for file path
* Add handling for non-source non-destination info, pull out markdown listing
* feat: Add airbyte-cron Helm chart
* New chart resides in `charts/airbyte-cron`
* Updated the parent chart (`airbyte`) `values.yaml` to include config
key for `cron`
* Add airbyte-cron to release workflow
* chore: remove TEMPORAL_* vars
Co-authored-by: Kyryl Skobylko <xpuska513@gmail.com>
Buildpulse.io is a tool for detecting flaky tests that integrates well with GHA. Flaky tests are something we want to start figuring out more of.
This PR starts pushing platform tests to buildpulse so we can start trialing out this tool.
The idea is to try this out for a couple of weeks (enough time to see if this tool actually can detect flaky tests) and decide if this serves our needs.
* test pull request for testing testing-tool commands
* test pull request for testing testing-tool commands
* add command for run testing tool in main repo
* small changes for test e2e testing tool commands
* small changes for test e2e testing tool commands
* test pull request for testing testing-tool commands
* test pull request for testing testing-tool commands
* add command for run testing tool in main repo
* add github action for help-full command processing
* test pull request for testing testing-tool commands
* test pull request for testing testing-tool commands
