-
Notifications
You must be signed in to change notification settings - Fork 21
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
Remove FLOWDB_SERVICES env var #831
Conversation
Codecov Report
@@ Coverage Diff @@
## master #831 +/- ##
=======================================
Coverage 93.14% 93.14%
=======================================
Files 130 130
Lines 6552 6552
Branches 695 695
=======================================
Hits 6103 6103
Misses 330 330
Partials 119 119
Continue to review full report at Codecov.
|
1 similar comment
Codecov Report
@@ Coverage Diff @@
## master #831 +/- ##
=======================================
Coverage 93.14% 93.14%
=======================================
Files 130 130
Lines 6552 6552
Branches 695 695
=======================================
Hits 6103 6103
Misses 330 330
Partials 119 119
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #831 +/- ##
=======================================
Coverage 93.07% 93.07%
=======================================
Files 130 130
Lines 6552 6552
Branches 695 695
=======================================
Hits 6098 6098
Misses 330 330
Partials 124 124
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, apart from a couple of small comments. Given the way the Makefile has changed, I thikn this is cleaner than having two different env vars to select the services.
Given that the intention is now to pass a list of services (rather than assuming we will usually want to spin up everything), I'm not sure how much benefit there is to have all the separate make targets (e.g. make flowmachine-up
when we could instead run DOCKER_SERVICES=flowmachine make up
). I'm happy to keep them in for now, though, to wait and see how we use this in practice. I imagine the individual make *-build
targets will continue to be useful, in any case.
Co-Authored-By: James Harrison <[email protected]>
…r/FlowKit into remove-flowdb-services-env-var
Closes #827
I have:
Description
This PR removes the
FLOWDB_SERVICES
env var from the toplevel Makefile, so that nowDOCKER_SERVICES
is the only variable that controls which services are spun up uponmake up
.This isn't the only possible solution. I actually like @greenape's suggestions for an alternative tweak. The reason why I chose to remove this env var is because now that we also have
flowetl
and theworked_examples
in theDOCKER_SERVICES
there are even more possible combinations that the user may want (previously it was basically just about which version of flowdb to cheose), so it feels clunky and somewhat error-prone to support the different use cases via different env vars in the Makefile. The cleaner solution seems to me to only haveDOCKER_SERVICES
in the Makefile, and if we want more flexibility we should be moving towards proper build and startup scripts (which is probably a good idea anyway, because I think we're duplicating this functionality in a few places in various build scripts).Anyway, just my current view on it. Happy to discuss, and also to change this PR if a different solution is more desirable.