* Removing JIRA Connector Domain Pattern
The pattern for the JIRA domain will not necessarily end in atlassian.net. (e.g. cloud hosted JIRA can also be jira.com and on premise installations can also deviate from this pattern).
I propose removing this restriction. Our opinion is that it's too strict and brings little to no value.
This PR fixes: https://github.com/airbytehq/airbyte/issues/7502
* Bump version
* Updated description
Co-authored-by: Willi Müller <willi.mueller@posteo.de>
* update examples
* update oss_catalog seed file
* update docker version
* Update docs
* auto-bump connector version
---------
Co-authored-by: Willi Müller <willi.mueller@posteo.de>
Co-authored-by: Marcos Marx <marcosmarxm@users.noreply.github.com>
Co-authored-by: Octavia Squidington III <octavia-squidington-iii@users.noreply.github.com>
* Fix expected records for hubspot and intercom
* Fix typo for intercom
* Fix close com, fecebook marketing, freshsales, greenhouse expected records
* Fix intercom CAT
* Fix unittest for new pydentic version
* Fix facebook marketing unittests and jira CAT
* Fix formating for facebook marketing, jira and CAT for monday
* Fix pipedrive and recharge CAT
* Fix CAT for Slack, Strava, Stripe, Trello and Twitter
* Fix expected records for slack
* Fix CAT for Youtube and Sentry
* Fix unittests for mixpanel
* Added allowedHosts and fix facebook marketing CAT
* Fix CAT for Faker and Twillio
* Fix expected records for hubspot
* Fix expected records for Sentry
* Fix check status for GAv4
Scripts to
* Run CATs against the local CDK for one connector
* Run CATs against the local CDK for multiple connectors
* Create a connecter image with the local CDK
---------
Co-authored-by: Alexandre Girard <alexandre@airbyte.io>
Co-authored-by: Sherif A. Nada <snadalive@gmail.com>
* Expected Records to `.jsonl` format
* fix formatting template
* remove endline
* update templates
* Update docs/connector-development/testing-connectors/source-acceptance-tests-reference.md
Co-authored-by: Pedro S. Lopez <pedroslopez@me.com>
Co-authored-by: Pedro S. Lopez <pedroslopez@me.com>
* 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
* Include tcp port in Clickhouse destination configuration for normalization
* revert custom dbt on clickhouse
* Bumpversion of destination connector
* Format code
* Add pull requests stream
* Add id field
* Fix to work with latest commits
* Add docs and prevent failures
* bump connector version
* run seed file
Co-authored-by: Chris Wu <chris@faros.ai>
* Add option to render fields in HTML format and fix sprint_issue ids
* Bump connector version
* run format
* run format
* run seed generaotr
* run format
Co-authored-by: Chris Wu <chris@faros.ai>
* Create separate cache file per stream and add projects and start_date config
* Add project id to issue record
* Add projectId to issue schema
* Add BoardIssues stream
* Add SprintIssues stream
* Add Epics stream and deduplicate state code
* Add EpicIssues stream and additional fields for Issues stream
* Add story points to sprint issues
* Add new streams to test catalog
* Update gitignore
* Rename cache boolean and fix test catalog
* Fix streams that depend on Issues stream
* Fix sprint_issues stream
* Add more fields to issues stream and format
* Add option to expand issue changelogs
* Remove epic_issues stream
* Expand project descriptions
* Show rendered fields for epics
* Include project key
* Include project key in issues stream
* Address comments
* Use CDK caching
* Remove extra changes
* Fix sprints stream reading from non-scrum boards
* Format
* small fix and bump version
* bump version
Co-authored-by: Chris Wu <chris@faros.ai>
* Create separate cache file per stream and add projects and start_date config
* Add project id to issue record
* Add projectId to issue schema
* Add BoardIssues stream
* Add SprintIssues stream
* Add Epics stream and deduplicate state code
* Add EpicIssues stream and additional fields for Issues stream
* Add story points to sprint issues
* Add new streams to test catalog
* Update gitignore
* Rename cache boolean and fix test catalog
* Fix streams that depend on Issues stream
* Fix sprint_issues stream
* Add more fields to issues stream and format
* Add option to expand issue changelogs
* Remove epic_issues stream
* Expand project descriptions
* Show rendered fields for epics
* Include project key
* Include project key in issues stream
* Address comments
* Use CDK caching
* Remove extra changes
* Fix sprints stream reading from non-scrum boards
* Format
Wrapper around Prometheus lib to interface with Datadog.
We use prometheus because:
- Future-proofing as it's uses the general open metrics format.
- Prometheus makes it's metrics available to a scraper to it lends itself better to the OSS set up.
- Datadog automatically converts promethues metrics into dd metrics so we don't lose much.
source-acceptance-test framework not longer required json_schema parameters
from catalog file. This parameter is verbose, makes reading config file
complicated and could be misleading when debugging acceptance test issues.
Co-authored-by: Dmytro Rezchykov <dmitry.rezchykov@zazmic.com>
* pre-setup save
* save labels
* modify schemas (test)
* rm unused
* add newlines to schemas
* remove incremental as it was before
* fixing file
* format && fixes
* update docs
Introduce a better port abstraction whose primary purpose is to confirm that ports are released when the Kube Pod Process is closed.
This prevents issues like #4660
I'm also opening more ports so we can run at least 10 syncs in parallel.
