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

Add a feature flag for a failure because of an heartbeat failed check #22036

Merged
merged 6 commits into from
Feb 7, 2023

Conversation

benmoriceau
Copy link
Contributor

What

Add a feature flag that will then be used to protect jobs from failing because of a missed heartbeat.

@benmoriceau benmoriceau temporarily deployed to more-secrets January 27, 2023 22:18 — with GitHub Actions Inactive
@benmoriceau benmoriceau temporarily deployed to more-secrets January 27, 2023 22:18 — with GitHub Actions Inactive
@github-actions
Copy link
Contributor

github-actions bot commented Jan 27, 2023

Airbyte Code Coverage

There is no coverage information present for the Files changed

Total Project Coverage 24.52%

Copy link
Member

@colesnodgrass colesnodgrass left a comment

Choose a reason for hiding this comment

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

  • camelCase the flag for consistency with other flags
  • create this flag in LD (if you haven't yet)

@@ -1,3 +1,5 @@
flags:
- name: performance.backgroundJsonSchemaValidation
enabled: true
- name: heartbeat.fail_sync
Copy link
Member

Choose a reason for hiding this comment

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

The docs are up yet, but the existing feature-flags are all camelCased. Could we camelCase this one for consistency?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

@benmoriceau benmoriceau temporarily deployed to more-secrets January 31, 2023 01:57 — with GitHub Actions Inactive
@benmoriceau benmoriceau temporarily deployed to more-secrets January 31, 2023 01:57 — with GitHub Actions Inactive
Copy link
Contributor

@jdpgrailsdev jdpgrailsdev left a comment

Choose a reason for hiding this comment

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

:shipit:

@colesnodgrass
Copy link
Member

@benmoriceau heads-up that the flags.yml file was moved to the root directory in #22158

@benmoriceau
Copy link
Contributor Author

@colesnodgrass could you review the flag in LD? https://app.launchdarkly.com/default/production/features/heartbeat.failSync/targeting It is the first one, I'm creating and I would like to make sure that I didn't do a mistake.

@octavia-squidington-iii octavia-squidington-iii added the area/frontend Related to the Airbyte webapp label Feb 6, 2023
@benmoriceau benmoriceau temporarily deployed to more-secrets February 6, 2023 02:47 — with GitHub Actions Inactive
@benmoriceau benmoriceau temporarily deployed to more-secrets February 6, 2023 02:47 — with GitHub Actions Inactive
@octavia-squidington-iii octavia-squidington-iii removed the area/frontend Related to the Airbyte webapp label Feb 6, 2023
@benmoriceau benmoriceau temporarily deployed to more-secrets February 6, 2023 04:44 — with GitHub Actions Inactive
@benmoriceau benmoriceau temporarily deployed to more-secrets February 6, 2023 04:44 — with GitHub Actions Inactive
@benmoriceau benmoriceau temporarily deployed to more-secrets February 6, 2023 07:13 — with GitHub Actions Inactive
@benmoriceau benmoriceau temporarily deployed to more-secrets February 6, 2023 07:14 — with GitHub Actions Inactive
@benmoriceau benmoriceau merged commit 53098fe into master Feb 7, 2023
@benmoriceau benmoriceau deleted the bmoric/source-hearbeat-feature-flags branch February 7, 2023 19:45
danidelvalle pushed a commit to danidelvalle/airbyte that referenced this pull request Feb 9, 2023
…airbytehq#22036)

* Add a feature flag for a failure because of an heartbeat failed check

* Use Camel case

* Add missing new line

* Checkout From master
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.

4 participants