disable galaxy config sorting#218
disable galaxy config sorting#218sanjaysrikakulam wants to merge 1 commit intogalaxyproject:mainfrom
Conversation
By default, sort_keys is set to true in the to_nice_yaml function. Sorting the brand_by_host affects the branding of the subdomains, especially when the root domain is added before the subdomain brand due to the sorting.
|
ping @natefoo |
jdavcs
left a comment
There was a problem hiding this comment.
Looks good to me. Sorry for the delayed review!
On second thought, I have a concernt about this change. I'll post a comment separately.
|
I don't think this is the right solution. This unsets the default sort for all galaxy config properties. We don't view the generated config often, but when we do, it helps when those options are sorted. |
|
@jdavcs its not solved, you see it here: https://virology.usegalaxy.eu/ |
|
If disabling sorting does not break idempotency this is probably ok, although I would prefer this would be configurable. IMO the real solution is for Galaxy to read these config options correctly. It should not be matching |
In EU @bgruening observed that the brand_by_host gets sorted in the final configuration when written to disk (
galaxy.ymlfile). As a result of this sorting, the usegalaxy.eu: Europe comes before the subdomain virology.usegalaxy.eu: Virology, which leads to the misbranding of the subdomain https://virology.usegalaxy.eu. This subdomain contains the brandEuropeinstead ofVirology.Example (final config from
galaxy.yml):By default,
sort_keysis set totruein theto_nice_yamlfunction in thegalaxy.yml.j2template. Sorting thebrand_by_hostin Galaxy config affects the branding of the subdomains. Therefore, this PR disables the defaultsort_keys.@natefoo, I am unsure whether the default sorting is needed for anything in Galaxy configuration. Please correct me if this is not the case.