## What
We have a workflow that once a day checks if the latest CDK version
would break any connector. If there are test failures, it sends a slack
alert. In addition to sending a slack alert, we would like to get an
oncall ticket in our github project. We should only do this for
destinations (connectors owned by move)
## How
Added a few extra steps to the workflow that calls a script that creates
gh issues. It checks if an issue already exists for the connector. If it
does it will update the description with information about the new
failure. If it doesn't it will create a new ticket
## How did I test this?
Tested in this PR https://github.com/airbytehq/airbyte/pull/67617.
Confirmed that tickets were created if they didn't exist and that they
were updated if they did exist.
## Can this PR be safely reverted and rolled back?
<!--
* If unsure, leave it blank.
-->
- [x] YES 💚
- [ ] NO ❌
## What
The existing `CDK Connector Compatibility Test` workflow currently tests
all connectors using the bulk CDK. However, we only want to test
certified connectors. This PR modifies the workflow to run tests
exclusively on certified connectors using the CDK.
## How
Instead of getting the list of connectors to test from the diff
generated by running a CDK upgrade task, we will get the list of
certified connectors by reusing the script used in the auto bump
workflow to get this information.
## How did I test this?
Tested it in [this](https://github.com/airbytehq/airbyte/pull/67605) PR.
More specifically, here's the PR check run
https://github.com/airbytehq/airbyte/actions/runs/18410594109/job/52461620803?pr=67605
Note: it looks like the connectors we are testing didn't change. I'd
guess it is possible that in the future we will have some none certified
connectors using the cdk so the change in this PR still makes sense.
## Can this PR be safely reverted and rolled back?
<!--
* If unsure, leave it blank.
-->
- [x] YES 💚
- [ ] NO ❌
* Rename to connector test report
* Get all test outputs
* Get last 10 output for all connectors
* Get runs by connector
* Crudely write badge and summary
* Add render functions
* Update connector report badge and link
* Fix url link
* Fix qa report tests
* update qa-engine tests
* Move regex to resource
* Add cron
* Run format
* New line
* Make badge green if last is successful
* Fix test
* Remove report.sh and build_report.py
---------
Co-authored-by: Octavia Squidington III <octavia-squidington-iii@sers.noreply.github.com>
* Adds support for incremental syncs with GLOBAL state message emission
* Adds args to Source to not break, future work is to add same features to Source perf-harness and ./gradlew :spotlessJavaApply
* Adds support for pseudo-parallel datasets
* Ran ./gradlew :spotlessJavaApply
* Automated Change
* Fixes issue with parallel datasets credentials
* Fixes filter for parallel credentials
* Adds a new configurable property to build a pseudo-parallel catalog
* Fixes Github Actions variable to be processed properly with the K8s harness yaml
* Adds unit test for random streams and generating streams within the same configured catalog
* Ran ./gradlew :spotlessJavaApply
* Added additional description for GitHub Actions
* Update connector-performance-command.yml
Moved text up to connect with other argument discussion
* Fixes spotBugs issue
* Automated Commit - Formatting Changes
* Update GitHub Action description
---------
Co-authored-by: ryankfu <ryankfu@users.noreply.github.com>
Co-authored-by: Rodi Reich Zilberman <867491+rodireich@users.noreply.github.com>
* remove arguments
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* Source Performance harness (#23922)
* test
* initial commit
* Working dev
* src-platform-dst
* Integrate secrets
* Update .dockerignore
* Update build.gradle
* Update base.sh
* Build harness module and use it to measure
* Build harness module and use it to measure
* Build harness module and use it to measure
* Automated Change
* Integrate secrets
* Integrate secrets
* Integrate secrets
* Integrate secrets
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* Automated Change
* test
* Automated Change
* better error handling
* temp
* Automated Change
* use connector image name
* use connector image name
* use connector image name
* use connector image name
* use connector image name
* use connector image name
* use connector image name
* use connector image name
* add test name argument
* add test name argument
* add test name argument
* add test name argument
* add test name argument
* add test name argument
* Automated Change
* add bottleneck_stream1 dataset
* Automated Change
* fix dependency
* fix dependency
* test downgrade of commons to 41.1
* Automated Change
* test downgrade of commons to 41.0
* test
* test
* test
* test
* test
* exit condition
* exit condition
* exit condition
* test
* test
* test
* test
* test
* test
* sanity
* readme
* change command name
* update gradle settings
* sanity
* architecture aware docker build
* sanity
* put run harness step in a script
* sanity
* sanity
---------
Co-authored-by: rodireich <rodireich@users.noreply.github.com>
* Updates docusaurus
* Small docs fixes
deploy_docusaurus info messages are changed to
reflect reality
updates a secret to exist
* Go back to the right branch after deploy
dev runs of this pr can be found here: https://github.com/airbytehq/airbyte/actions/workflows/release-airbyte-os.yml
I've tested the `create_release` step for both `airbyte` and `airbyte-platform`.
What I haven't tested are:
- publishing docker images step for airbyte-platform
- the auto commit steps for both.
What also should be noted: the artifacts from the `run-ab-platform.sh` script need to be commited into the repo for them to be included in the release.
* delete platform code and workflows
* delete more platform workflows
* sunset kustomize (#23187)
* sunset kustomize
* remove build steps that use kustomize
* remove k8s kustomize gke-kube-acceptance-tests
* delete docker-compose files
* remove platform from check_images_exist.sh
* Working replacement script for docker
* rename start script and add download files to gitignore
* add args and download only option
* integration test downloads docker compose files
* remove helm charts
* remove more platform files
* add flags.yml
* use version from gradle.properties instead of .env
* Working replacement script for docker (#23227)
* Working replacement script for docker
* Working debugging line
* rename start script and add download files to gitignore
* add args and download only option
* Made flags cleaner and more cleanup
i've never used this flag pattern, its much
easier than my usual way
* warn about a sharp edge
* Don't run when we don't know a command
* better help spacing
* add flags.yml
---------
Co-authored-by: cpdeethree <conor@airbyte.io>
Co-authored-by: Conor <cpdeethree@users.noreply.github.com>
* remove more-secrets env
---------
Co-authored-by: Charles <charles@airbyte.io>
Co-authored-by: Topher Lubaway <asimplechris@gmail.com>
