Uh oh!
There was an error while loading. Please reload this page.
Add cockroach db support - #499
Conversation
Uh oh!
There was an error while loading. Please reload this page.
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
commented
Dec 9, 2017
Please ignore my last point, we'll include small modules in core for now 😃 |
kiview
left a comment
There was a problem hiding this comment.
Can you please also add a test for CockroachContainer? Or am I missing something and it's tested implicitly?
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
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
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! |
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. |
rnorth
commented
Jan 8, 2019
We should keep this open. Sent with GitHawk |
kiview
commented
Jan 8, 2019
@tolkonepiu Sorry for keeping thins dangling so long. |
bsideup
commented
Jan 8, 2019
@kiview let's drop the self typing |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
rnorth
commented
May 27, 2019
I'll take on @bsideup's comment. |
Use an appropriate default test database (see cockroachdb/cockroach#19826 (comment))
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 |
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. |
rnorth
commented
Aug 26, 2019
Not stale - reopening. |
reinierbos
commented
Sep 20, 2019
Any idea when this PR will be merged to master (and then released)? I would love to start using it! |
| super(dockerImageName); | ||
| withExposedPorts(REST_API_PORT, DB_PORT); | ||
| withEnv("COCKROACH_USER", username); |
There was a problem hiding this comment.
Done (disabling these settings, since they don't work!)
Since there is no current way to make them do what we want
Add support for CockroachDB