Skip to content

Baragon-0.2.0
Compare
Choose a tag to compare
@ssalinas ssalinas released this 04 Apr 14:58
Baragon-0.2.0
b2a9723

Check out the 0.2.0 Milestone to see all bug fixes and features in detail.

Upgrading

It is recommended to upgrade BaragonService before BaragonAgentService for this release. However, the new multiple domains feature will not function correctly until both components are updated.

New Features

  • #162 - Support locking additional paths for a single service
  • #165 - Support for regex-based paths
  • #167 - Support for multiple domains in a single group (extra variables in template path, render multiple per template)

Other Changes and Bug Fixes

  • #164 - Upgrade basepom
  • #163 - Better base path conflict message
  • #161 - Ensure a duplicate upstream with no rack is not deleted
  • #160 - Lock brunch to 2.2.x
  • #157 / #158 - Additional handlebars helpers for dealing with racks/weighting
  • #156 - UI improvements and bump to brunch 2
  • #154 - Upgrade Horizon version
  • #152 - Only render templates if they are not empty
  • #151 - Handle a null Stat from zk
  • #150 - Don't require base path lock for a service delete with no upstreams

Deprecations

  • In LoadBalancerConfiguration (Baragon Agent configuration field), the domain field is now deprecated. Due to the fact that a single agent can now support multiple domains, the domain field in the loadBalancerConfig section has been replaced with defaultDomain (String) and domains (List) fields. Either domain or defaultDomain may be specified, however defaultDomain will take precedence and domain will be removed in the next release. This change is also reflected in the BaragonGroup object.
  • In BaragonAgentMetadata the domain field will be removed in the next release. Domain information will instead only be available in the BaragonGroup object which is updated by the agent at startup time

Thanks

@jhaber
@mhrabovcin
@tpetr

Assets 2
Loading