Skip to content

✨ Source S3: v4 rollout - #29757

Closed
Maxime Carbonneau-Leclerc (maxi297) wants to merge 25 commits into
masterfrom
source-s3-v4-rollout/v4-rollout
Closed

Maxime Carbonneau-Leclerc (maxi297) wants to merge 25 commits into
masterfrom
source-s3-v4-rollout/v4-rollout

Conversation

@maxi297

Copy link
Copy Markdown
Contributor

What

Describe what the change is solving
It helps to add screenshots if it affects the frontend.

How

Describe the solution

Recommended reading order

  1. x.java
  2. y.python

🚨 User Impact 🚨

Are there any breaking changes? What is the end result perceived by the user?

For connector PRs, use this section to explain which type of semantic versioning bump occurs as a result of the changes. Refer to our Semantic Versioning for Connectors guidelines for more information. Breaking changes to connectors must be documented by an Airbyte engineer (PR author, or reviewer for community PRs) by using the Breaking Change Release Playbook.

If there are breaking changes, please merge this PR with the 🚨🚨 emoji so changelog authors can further highlight this if needed.

Pre-merge Actions

Expand the relevant checklist and delete the others.

New Connector

Community member or Airbyter

  • Community member? Grant edit access to maintainers (instructions)
  • Unit & integration tests added and passing. Community members, please provide proof of success locally e.g: screenshot or copy-paste unit, integration, and acceptance test output. To run acceptance tests for a Python connector, follow instructions in the README. For java connectors run ./gradlew :airbyte-integrations:connectors:<name>:integrationTest.
  • Connector version is set to 0.0.1
    • Dockerfile has version 0.0.1
  • Documentation updated
    • Connector's README.md
    • Connector's bootstrap.md. See description and examples
    • docs/integrations/<source or destination>/<name>.md including changelog with an entry for the initial version. See changelog example
    • docs/integrations/README.md

Airbyter

If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.

  • Create a non-forked branch based on this PR and test the below items on it
  • Build is successful
  • If new credentials are required for use in CI, add them to GSM. Instructions.
Updating a connector

Community member or Airbyter

  • Grant edit access to maintainers (instructions)
  • Unit & integration tests added

Airbyter

If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.

  • Create a non-forked branch based on this PR and test the below items on it
  • Build is successful
  • If new credentials are required for use in CI, add them to GSM. Instructions.
Connector Generator
  • Issue acceptance criteria met
  • PR name follows PR naming conventions
  • If adding a new generator, add it to the list of scaffold modules being tested
  • The generator test modules (all connectors with -scaffold in their name) have been updated with the latest scaffold by running ./gradlew :airbyte-integrations:connector-templates:generator:testScaffoldTemplates then checking in your changes
  • Documentation which references the generator is updated as needed

@octavia-squidington-iii Octavia Squidington III (octavia-squidington-iii) added area/connectors Connector related issues area/documentation Improvements or additions to documentation connectors/source/s3 labels Aug 23, 2023
@github-actions

github-actions Bot commented Aug 23, 2023 •

Copy link
Copy Markdown
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.

@maxi297 Maxime Carbonneau-Leclerc (maxi297) changed the title Source s3 v4 rollout/v4 rollout ✨ Source S3: v4 rollout Aug 23, 2023
@github-actions

Copy link
Copy Markdown
Contributor

source-s3 test report (commit 25136241ee) - ❌

⏲️ Total pipeline duration: 11mn07s

Step Result
Connector package install ✅
Build source-s3 docker image for platform linux/x86_64 ✅
Unit tests ✅
Integration tests ✅
Acceptance tests ❌
Code format checks ❌
Validate airbyte-integrations/connectors/source-s3/metadata.yaml ✅
Connector version semver check ✅
Connector version increment check ✅
QA checks ❌

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=source-s3 test

@github-actions

Copy link
Copy Markdown
Contributor

source-s3 test report (commit 6af59b683c) - ❌

⏲️ Total pipeline duration: 11mn01s

Step Result
Connector package install ✅
Build source-s3 docker image for platform linux/x86_64 ✅
Unit tests ✅
Integration tests ✅
Acceptance tests ✅
Code format checks ✅
Validate airbyte-integrations/connectors/source-s3/metadata.yaml ✅
Connector version semver check ✅
Connector version increment check ✅
QA checks ❌

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=source-s3 test

@github-actions

Copy link
Copy Markdown
Contributor

source-s3 test report (commit 6af59b683c) - ❌

⏲️ Total pipeline duration: 09mn16s

Step Result
Connector package install ✅
Build source-s3 docker image for platform linux/x86_64 ✅
Unit tests ✅
Integration tests ✅
Acceptance tests ✅
Code format checks ✅
Validate airbyte-integrations/connectors/source-s3/metadata.yaml ✅
Connector version semver check ✅
Connector version increment check ✅
QA checks ❌

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=source-s3 test

@github-actions

Copy link
Copy Markdown
Contributor

source-s3 test report (commit 2bf73a928a) - ❌

⏲️ Total pipeline duration: 11mn11s

Step Result
Connector package install ✅
Build source-s3 docker image for platform linux/x86_64 ✅
Unit tests ✅
Integration tests ✅
Acceptance tests ✅
Code format checks ✅
Validate airbyte-integrations/connectors/source-s3/metadata.yaml ✅
Connector version semver check ✅
Connector version increment check ✅
QA checks ❌

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=source-s3 test

@github-actions

Copy link
Copy Markdown
Contributor

source-s3 test report (commit ca7f891645) - ❌

⏲️ Total pipeline duration: 11mn23s

Step Result
Connector package install ✅
Build source-s3 docker image for platform linux/x86_64 ✅
Unit tests ✅
Integration tests ✅
Acceptance tests ✅
Code format checks ✅
Validate airbyte-integrations/connectors/source-s3/metadata.yaml ✅
Connector version semver check ✅
Connector version increment check ✅
QA checks ❌

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=source-s3 test

@github-actions

Copy link
Copy Markdown
Contributor

source-s3 test report (commit dceec7e847) - ❌

⏲️ Total pipeline duration: 11mn37s

Step Result
Connector package install ✅
Build source-s3 docker image for platform linux/x86_64 ✅
Unit tests ✅
Integration tests ✅
Acceptance tests ✅
Code format checks ✅
Validate airbyte-integrations/connectors/source-s3/metadata.yaml ✅
Connector version semver check ✅
Connector version increment check ✅
QA checks ❌

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=source-s3 test

@github-actions

Copy link
Copy Markdown
Contributor

source-s3 test report (commit f6062a18c6) - ❌

⏲️ Total pipeline duration: 11mn08s

Step Result
Connector package install ✅
Build source-s3 docker image for platform linux/x86_64 ✅
Unit tests ✅
Integration tests ✅
Acceptance tests ✅
Code format checks ✅
Validate airbyte-integrations/connectors/source-s3/metadata.yaml ✅
Connector version semver check ✅
Connector version increment check ✅
QA checks ❌

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=source-s3 test

@github-actions

Copy link
Copy Markdown
Contributor

source-s3 test report (commit 6bc1edf4b4) - ✅

⏲️ Total pipeline duration: 11mn30s

Step Result
Connector package install ✅
Build source-s3 docker image for platform linux/x86_64 ✅
Unit tests ✅
Integration tests ✅
Acceptance tests ✅
Code format checks ✅
Validate airbyte-integrations/connectors/source-s3/metadata.yaml ✅
Connector version semver check ✅
Connector version increment check ✅
QA checks ✅

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=source-s3 test

@github-actions

github-actions Bot commented Sep 2, 2023

Copy link
Copy Markdown
Contributor

source-s3 test report (commit 39c5be0ec6) - ✅

⏲️ Total pipeline duration: 09mn20s

Step Result
Connector package install ✅
Build source-s3 docker image for platform linux/x86_64 ✅
Unit tests ✅
Integration tests ✅
Acceptance tests ✅
Code format checks ✅
Validate airbyte-integrations/connectors/source-s3/metadata.yaml ✅
Connector version semver check ✅
Connector version increment check ✅
QA checks ✅

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=source-s3 test

@github-actions

github-actions Bot commented Sep 5, 2023

Copy link
Copy Markdown
Contributor

source-hubplanner test report (commit 0dc5cbdb07) - ❌

⏲️ Total pipeline duration: 01mn45s

Step Result
Connector package install ✅
Build source-hubplanner docker image for platform linux/x86_64 ✅
Acceptance tests ❌
Code format checks ✅
Validate airbyte-integrations/connectors/source-hubplanner/metadata.yaml ✅
Connector version semver check ✅
Connector version increment check ❌
QA checks ✅

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=source-hubplanner test

@maxi297

Copy link
Copy Markdown
Contributor Author

Superseded by #30147 to see if we could avoid autoformat

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/source/hubplanner connectors/source/s3

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants