Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update with master #55

Merged
merged 3,878 commits into from
Aug 22, 2024
Merged

update with master #55

merged 3,878 commits into from
Aug 22, 2024

Conversation

sc250072
Copy link

What

How

Review guide

User Impact

Can this PR be safely reverted and rolled back?

  • YES 💚
  • NO ❌

edgao and others added 29 commits August 21, 2024 20:18
… from `CRMSearchStream` class (#44538)

Co-authored-by: Alexandre Girard <[email protected]>
## What
I tried to get the CAT tests running on airbyte-enterprise today. There were a few failures which surfaced bugs in the Bulk CDK, which doesn't always emit STATE or TRACE ERROR messages when required during a READ.

## How
Emit TRACE ERROR messages if the configured streams are bad.
Emit at least one STATE message for each stream with an input state.

## Review guide
Commit by commit

## User Impact
None

## Can this PR be safely reverted and rolled back?
<!--
* If unsure, leave it blank.
-->
- [x] YES 💚
- [ ] NO ❌
…e metadata model (#44504)

## What
Closes airbytehq/airbyte-internal-issues#9249

## How
* Add a `RolloutConfiguration.yaml` model
* Reference it in the connector metadata model under the `releases` field.
* Introduce a `isReleaseCandidate` field in under `releases`
* Re-generated pydantic models
…dates (#44509)

## What
Relates to airbytehq/airbyte-internal-issues#9403

When a connector metadata is flagged as a release candidate we should upload it to a dedicated path in GCS, so that it will not be picked up by the registry as the latest version.
## What
Closes airbytehq/airbyte-internal-issues#9403
When a connector is a release candidate it will have the `releases.isReleaseCandidate` flag set to `true` in its `metadata.yaml`.
We don't want to publish the `latest` tag when the connector is a RC.

## How
Tweak the publish pipeline to conditionnaly publish the latest tag according to the metadata content.
@sc250072 sc250072 merged commit 5d73d92 into Teradata:teradata_master Aug 22, 2024
10 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.