Github user aledsage commented on the issue:
https://github.com/apache/brooklyn-server/pull/916
@nakomis @sjcorbett @tbouron are you suggesting we change the
`AutoScalerPolicy` etc to do that, or that we leave it as-is so the auto-scaler
doesn't work well with `maxSize` (unless the user duplicates the config in both
the cluster and the policy)?
If it was just the UI/CLI, I'd be fine with leaving as-is. The human who
called it would get feedback immediately that it failed, and would then know to
try again. My issue is with programmatic usage - we need to do one of: 1) leave
as-is so that users of auto-scaler etc need to duplicate the `maxSize` config;
2) change `DynamicCluster` as I'm suggesting; or 3) change the programmatic
usage of `resize` (but auto-scaler works with anything that is resizable,
whereas `maxSize` is only defined on `DynamicCluster`.
---
