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

Destination redshift: Upgrade cdk #35316

Merged
merged 8 commits into from
Mar 5, 2024

Conversation

edgao
Copy link
Contributor

@edgao edgao commented Feb 15, 2024

No description provided.

@edgao edgao requested a review from a team as a code owner February 15, 2024 00:19
Copy link

vercel bot commented Feb 15, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
airbyte-docs ⬜️ Ignored (Inspect) Visit Preview Mar 4, 2024 7:59pm

Copy link
Contributor

Before Merging a Connector Pull Request

Wow! What a great pull request you have here! 🎉

To merge this PR, ensure the following has been done/considered for each connector added or updated:

  • PR name follows PR naming conventions
  • Breaking changes are considered. If a Breaking Change is being introduced, ensure an Airbyte engineer has created a Breaking Change Plan.
  • Connector version has been incremented in the Dockerfile and metadata.yaml according to our Semantic Versioning for Connectors guidelines
  • You've updated the connector's metadata.yaml file any other relevant changes, including a breakingChanges entry for major version bumps. See metadata.yaml docs
  • Secrets in the connector's spec are annotated with airbyte_secret
  • All documentation files are up to date. (README.md, bootstrap.md, docs.md, etc...)
  • Changelog updated in docs/integrations/<source or destination>/<name>.md with an entry for the new version. See changelog example
  • Migration guide updated in docs/integrations/<source or destination>/<name>-migrations.md with an entry for the new version, if the version is a breaking change. See migration guide example
  • If set, you've ensured the icon is present in the platform-internal repo. (Docs)

If the checklist is complete, but the CI check is failing,

  1. Check for hidden checklists in your PR description

  2. Toggle the github label checklist-action-run on/off to re-run the checklist CI.

@edgao edgao marked this pull request as draft February 15, 2024 15:28
@edgao edgao force-pushed the edgao/staging_csv_timestamp_timezone_redshift branch from 482afa8 to d282a36 Compare February 15, 2024 15:29
@edgao edgao force-pushed the edgao/staging_csv_timestamp_timezone branch from 3829bea to bbe9cde Compare February 21, 2024 00:28
@edgao edgao force-pushed the edgao/staging_csv_timestamp_timezone_redshift branch 2 times, most recently from babe364 to f267825 Compare February 21, 2024 16:11
@edgao edgao force-pushed the edgao/staging_csv_timestamp_timezone branch from bbe9cde to 9f7d650 Compare February 21, 2024 16:11
@edgao edgao force-pushed the edgao/staging_csv_timestamp_timezone_redshift branch from f267825 to 3b63113 Compare February 21, 2024 20:34
@edgao edgao force-pushed the edgao/staging_csv_timestamp_timezone branch from 9f7d650 to 863ef4a Compare February 21, 2024 20:34
@edgao edgao force-pushed the edgao/staging_csv_timestamp_timezone_redshift branch from 3b63113 to f3e8a21 Compare February 21, 2024 20:45
@edgao edgao force-pushed the edgao/staging_csv_timestamp_timezone branch from 863ef4a to 74528dc Compare February 21, 2024 20:45
@edgao edgao force-pushed the edgao/staging_csv_timestamp_timezone_redshift branch from f3e8a21 to 6569772 Compare February 21, 2024 21:32
@edgao edgao force-pushed the edgao/staging_csv_timestamp_timezone branch 2 times, most recently from eaad0b5 to 9e0fabb Compare February 21, 2024 21:43
@edgao edgao force-pushed the edgao/staging_csv_timestamp_timezone_redshift branch 2 times, most recently from 03fb969 to 97b1300 Compare February 21, 2024 21:51
@octavia-squidington-iii octavia-squidington-iii added the CDK Connector Development Kit label Feb 21, 2024
@edgao edgao force-pushed the edgao/staging_csv_timestamp_timezone branch 2 times, most recently from d128fa1 to d2f5c90 Compare February 21, 2024 22:03
@edgao edgao force-pushed the edgao/staging_csv_timestamp_timezone_redshift branch from 97b1300 to 70fe20b Compare February 21, 2024 22:04
@octavia-squidington-iii octavia-squidington-iii removed the CDK Connector Development Kit label Feb 21, 2024
@gisripa gisripa force-pushed the edgao/staging_csv_timestamp_timezone_redshift branch from aa1079d to 2ff6282 Compare March 4, 2024 19:43
@octavia-squidington-iii octavia-squidington-iii added the area/documentation Improvements or additions to documentation label Mar 4, 2024
Signed-off-by: Gireesh Sreepathi <[email protected]>
@gisripa gisripa merged commit b254a64 into master Mar 5, 2024
33 checks passed
@gisripa gisripa deleted the edgao/staging_csv_timestamp_timezone_redshift branch March 5, 2024 17:15
xiaohansong pushed a commit that referenced this pull request Mar 7, 2024
Signed-off-by: Gireesh Sreepathi <[email protected]>
Co-authored-by: Gireesh Sreepathi <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/connectors Connector related issues area/documentation Improvements or additions to documentation connectors/destination/redshift
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants