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 cockroach db support #499

Merged
merged 20 commits into from
Oct 3, 2019
Merged

Conversation

tolkonepiu
Copy link
Contributor

Add support for CockroachDB

@kiview
Copy link
Member

kiview commented Nov 28, 2017

Hi @tolkonepiu, thanks for the PR. I think our current approach advises to add such functionality as a module in a seperate repo.

@rnorth We still encourage extra module repos, do we?

@kiview
Copy link
Member

kiview commented Dec 9, 2017

Please ignore my last point, we'll include small modules in core for now 😃

kiview
kiview previously requested changes Dec 10, 2017
Copy link
Member

@kiview kiview left a comment

Choose a reason for hiding this comment

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

Can you please also add a test for CockroachContainer? Or am I missing something and it's tested implicitly?

@rnorth
Copy link
Member

rnorth commented Feb 11, 2018

We're shortly going to be merging #574, which changes our build system to Gradle. This is in part intended to make contributions of modules easier (per #564), but unfortunately means that for a short while your PR is going to show merge conflicts with the master branch.

I just want to let you know we don't want to create new work for you: we'll take care of the merge conflicts shortly. Please don't worry - we're grateful for your PR and want to help integrate it soon. Thank you.

@rnorth
Copy link
Member

rnorth commented Feb 25, 2018

@tolkonepiu I've locally made changes to bring this into the new Gradle-based build, as we'd love to merge this soon.

Could you perhaps allow us to push to your fork so that I can make the necessary changes? This page describes the steps: https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/

Thank you in advance!

@stale
Copy link

stale bot commented Jan 7, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this is a mistake, please reply to this comment to keep it open. If there isn't one already, a PR to fix or at least reproduce the problem in a test case will always help us get back on track to tackle this.

@stale stale bot added the stale label Jan 7, 2019
@rnorth
Copy link
Member

rnorth commented Jan 8, 2019

We should keep this open.

Sent with GitHawk

@kiview kiview requested a review from bsideup as a code owner January 8, 2019 19:44
@stale stale bot removed stale labels Jan 8, 2019
@kiview
Copy link
Member

kiview commented Jan 8, 2019

@tolkonepiu Sorry for keeping thins dangling so long.
@rnorth I've fixed the merge conflicts, I think it's good to go?

@bsideup
Copy link
Member

bsideup commented Jan 8, 2019

@kiview let's drop the self typing

@testcontainers testcontainers deleted a comment Jan 11, 2019
@testcontainers testcontainers deleted a comment Jan 11, 2019
@rnorth
Copy link
Member

rnorth commented May 27, 2019

I'll take on @bsideup's comment.

@rnorth rnorth self-assigned this May 27, 2019
@rnorth rnorth requested review from kiview and bsideup May 27, 2019 20:41
@rnorth
Copy link
Member

rnorth commented May 28, 2019

FWIW I've raised this ticket around the current gap in our docs for new module contributors. I'd like to have a bit of a think about the third point specifically before merging this, but otherwise I'm fine with this new module at an overall level: #1503

@stale
Copy link

stale bot commented Aug 26, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this is a mistake, please reply to this comment to keep it open. If there isn't one already, a PR to fix or at least reproduce the problem in a test case will always help us get back on track to tackle this.

@stale stale bot added the stale label Aug 26, 2019
@rnorth
Copy link
Member

rnorth commented Aug 26, 2019

Not stale - reopening.

@stale stale bot removed the stale label Aug 26, 2019
@reinierbos
Copy link

Any idea when this PR will be merged to master (and then released)? I would love to start using it!

@rnorth rnorth dismissed kiview’s stale review October 1, 2019 19:50

Dismissing stale review

@rnorth rnorth added this to the next milestone Oct 1, 2019
super(dockerImageName);

withExposedPorts(REST_API_PORT, DB_PORT);
withEnv("COCKROACH_USER", username);
Copy link
Member

Choose a reason for hiding this comment

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

Should go to "configure" method

Copy link
Member

@rnorth rnorth Oct 3, 2019

Choose a reason for hiding this comment

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

Done (disabling these settings, since they don't work!)

Since there is no current way to make them do what we want
@rnorth rnorth requested a review from bsideup October 3, 2019 13:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants