In EU @bgruening observed that the brand_by_host gets sorted in the final configuration when written to disk (galaxy.yml file). 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 brand Europe instead of Virology.
Example (final config from galaxy.yml):
brand_by_host:
africa.usegalaxy.eu: Africa
annotation.usegalaxy.eu: Genome Annotation
...
...
...
usegalaxy.eu: Europe
virology.usegalaxy.eu: Virology
By default, sort_keys is set to true in the to_nice_yaml function in the galaxy.yml.j2 template. Sorting the brand_by_host in Galaxy config affects the branding of the subdomains. Therefore, this PR disables the default sort_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.
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.