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

feat(sql): Support for multiple SQL data sources #424

Merged
merged 5 commits into from
Nov 27, 2019
Merged

feat(sql): Support for multiple SQL data sources #424

merged 5 commits into from
Nov 27, 2019

Conversation

srekapalli
Copy link
Contributor

  • Conditionally add secondary liquibase target if configured.
  • Conditionally add secondary JOOQ (DSLContext) to target a different dialect than the primary source. If two connection pools exist and they both are of same dialect we will not create secondary JOOQ bean. (eg: application having 2 pools against the same datasource will not need a secondary JOOQ)
  • Configuration is backward compatible for the most part. Applications will need to wire up the JOOQ and pool as applicable on the app side of things.
  • Tests exercise taking in the new sql config and verifies the bean existence as expected.

Copy link
Contributor

@cfieber cfieber left a comment

Choose a reason for hiding this comment

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

LGTM - couple minor comments

@cfieber cfieber added the ready to merge Approved and ready for merge label Nov 27, 2019
@mergify mergify bot added the auto merged label Nov 27, 2019
@mergify mergify bot merged commit 89cbc0b into spinnaker:master Nov 27, 2019
claymccoy pushed a commit to claymccoy/kork that referenced this pull request Mar 3, 2020
Since Bitbuckets Server hooks are different from Bitbucket Cloud, now also
add support for the former, so can be triggered with on-prem.
This now also handles Bitbucket Server ping.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto merged ready to merge Approved and ready for merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants