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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added a variable to control airbyte-proxy timeout #19493

Merged

Conversation

marcelopio
Copy link
Contributor

What

Fixes #19290

How

Adding a default timeout on the proxy template files of airbyte

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? If yes, please merge this PR with the 馃毃馃毃 emoji so changelog authors can further highlight this if needed.

Pre-merge Checklist

Expand the relevant checklist and delete the others.

New Connector

Community member or Airbyter

  • Community member? Grant edit access to maintainers (instructions)
  • Secrets in the connector's spec are annotated with airbyte_secret
  • 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.
  • Code reviews completed
  • Documentation updated
    • Connector's README.md
    • Connector's bootstrap.md. See description and examples
    • docs/integrations/<source or destination>/<name>.md including changelog. See changelog example
    • docs/integrations/README.md
    • airbyte-integrations/builds.md
  • PR name follows PR naming conventions

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.
  • /test connector=connectors/<name> command is passing
  • New Connector version released on Dockerhub by running the /publish command described here
  • After the connector is published, connector added to connector index as described here
  • Seed specs have been re-generated by building the platform and committing the changes to the seed spec files, as described here
Updating a connector

Community member or Airbyter

  • Grant edit access to maintainers (instructions)
  • Secrets in the connector's spec are annotated with airbyte_secret
  • 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.
  • Code reviews completed
  • Documentation updated
    • Connector's README.md
    • Connector's bootstrap.md. See description and examples
    • Changelog updated in docs/integrations/<source or destination>/<name>.md including changelog. See changelog example
  • PR name follows PR naming conventions

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.
  • /test connector=connectors/<name> command is passing
  • New Connector version released on Dockerhub and connector version bumped by running the /publish command described here
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

Tests

Unit

Put your unit tests output here.

Integration

Put your integration tests output here.

Acceptance

Put your acceptance tests output here.

@murat-cetinkaya
Copy link

Some connecters like Zuora might take longer than 300 seconds. I'd suggest to increase it to 600 seconds.

@marcelopio
Copy link
Contributor Author

I think it should be a variable that people can configure in their .env. I will make the necessary change

@murat-cetinkaya
Copy link

That's even better. Thank you @marcelopio 聽馃檹馃徏

@octavia-squidington-iv octavia-squidington-iv added the area/documentation Improvements or additions to documentation label Nov 17, 2022
Copy link
Contributor

@evantahler evantahler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm sad that we need this change (because we have connectors which take over a minute to return their schema), but given that, this is a great change!

docs/operator-guides/configuring-airbyte.md Outdated Show resolved Hide resolved
airbyte-proxy/test.sh Outdated Show resolved Hide resolved
Co-authored-by: Evan Tahler <evantahler@gmail.com>
@marcelopio marcelopio changed the title Added a default airbyte proxy timeout of 5min Added a variable to control airbyte-proxy timeout Nov 18, 2022
@marcelopio
Copy link
Contributor Author

@evantahler @natalyjazzviolin Do we need anything more to get this merged? Thx!

@murat-cetinkaya
Copy link

I'm looking forward to it 馃槉

@evantahler
Copy link
Contributor

We are on a Thanksgiving Code Freeze (US holiday), but we will look at merging this in December (馃憤 from me @natalyjazzviolin)

@marcosmarxm
Copy link
Member

Hello 馃憢, first thank you for this amazing contribution.

We really appreciate the effort you've made to improve the project.
We ask you patience for the code review. Last month our team was focused on Hacktoberfest event and that probably left some PR without the proper feedback. And this week, due to the Thanksgiving US Holiday, most our team is out of office with their families. Another important piece of information why code won't be merge this week is: as a safety measure the core team has decided to freeze merging code to main branch to keep the release stable. Next week we'll return to you with the proper code review and update the status of your contribution.

If you have any questions feel free to send me a message in Slack!
Thanks!

@natalyjazzviolin natalyjazzviolin temporarily deployed to more-secrets November 28, 2022 16:10 Inactive
@natalyjazzviolin natalyjazzviolin temporarily deployed to more-secrets November 28, 2022 16:10 Inactive
@natalyjazzviolin
Copy link
Contributor

@marcelopio thanks for resolving the conflicts! I'm running all CI/CD checks here: #19831 as I am not able to run them here. Once those pass we should be good to go!

@alexchouraki
Copy link
Contributor

Hi!
Can't wait for this one to be merged, it will be really useful for our use of Airbyte! Any visibility on a timeline for this?
Thanks a lot @marcelopio :)

Copy link
Member

@marcosmarxm marcosmarxm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@marcelopio need to correct the file permission
image

@marcosmarxm marcosmarxm temporarily deployed to more-secrets December 12, 2022 13:16 — with GitHub Actions Inactive
@marcosmarxm
Copy link
Member

Tested in #20361 it is working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation Improvements or additions to documentation community
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Proxy causes Gateway Timeout for dynamic schema discovery
7 participants