-
Notifications
You must be signed in to change notification settings - Fork 1k
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
[22.01] Include gravity in sample config #13531
[22.01] Include gravity in sample config #13531
Conversation
(The startup errors are to be expected without a new gravity release) |
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!
Thanks @ic4f, then I'll cut a new gravity release |
@@ -12,6 +12,7 @@ | |||
import requests | |||
import yaml | |||
from boltons.iterutils import remap | |||
from gravity.util import settings_to_sample |
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.
I guess that it won't be possible for gravity to depend on galaxy-config
in the future, unless we refactor this.
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.
We could make it a local import, or publish the config schema separately, but I thought we can do this once we're trying to do this.
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.
This broke the test_galaxy_packages
tests on CircleCI, I guess because gravity
needs to be added to packages/config/requirements.txt
.
Before merging we should merge galaxyproject/gravity#42 and publish 0.11.0
How to test the changes?
(Select all options that apply)
License