GitHub user tbouron opened a pull request: https://github.com/apache/brooklyn-server/pull/358
Allow REST API to return the config key's constraints for catalog apps Based on https://github.com/apache/brooklyn-server/pull/354 (needs to be merged first) This changes the underlying structure of how the constraints are stored for the config keys. Instead of a single field `Predicates.and(Predicates...)`, there is a `Map<String, Predicate>` to store the keys and predicates to use. This allows the REST API to returns what constraint (keys) a config key is using. The validation still do a `AND` to validate the value. You can merge this pull request into a Git repository by running: $ git pull https://github.com/tbouron/brooklyn-server fix/parameter-contraints Alternatively you can review and apply these changes as the patch at: https://github.com/apache/brooklyn-server/pull/358.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #358 ---- commit d02e73ea87c60d517ac146c3888a7796ee74f7a3 Author: Thomas Bouron <thomas.bou...@cloudsoftcorp.com> Date: 2016-09-27T11:06:32Z Config keys and parameters can now be marked as "pinned" regardless of their priority commit bdd1f726cf4af3bfc9e3f66191cbf4b77520f243 Author: Thomas Bouron <thomas.bou...@cloudsoftcorp.com> Date: 2016-09-28T11:38:12Z Expose config keys constraints on the REST API ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---