[GitHub] brooklyn-server pull request #354: Config keys and parameters can now be mar...

[tbouron]

Github user tbouron closed the pull request at:

https://github.com/apache/brooklyn-server/pull/354


---
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.
---

[GitHub] brooklyn-server pull request #354: Config keys and parameters can now be mar...

[tbouron]

GitHub user tbouron opened a pull request:

https://github.com/apache/brooklyn-server/pull/354

Config keys and parameters can now be marked as "pinned"

The new behaviour is as follow:
- By default, config keys and parameters are `pinned = false`
- A blueprint can specify a config key or parameter as pinned by using 
`@CatalogConfig(pinned = true)` or in yaml `pinned: true`
- In case of config keys or parameters pinned in YAML, the priority is auto 
incremented to keep the order (code lost in [this 
commit](https://github.com/apache/brooklyn-server/commit/6f624c78b1e7fe72c6df1ecd297b922721b2c023#diff-5310fbeb1f42a3a4cf0508ea441440baL82))

Tests have been updated. Changes in docs and JSGUI coming soon.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tbouron/brooklyn-server fix/priority-vs-pinned

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/brooklyn-server/pull/354.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 #354


commit d02e73ea87c60d517ac146c3888a7796ee74f7a3
Author: Thomas Bouron 
Date:   2016-09-27T11:06:32Z

Config keys and parameters can now be marked as "pinned" regardless of 
their priority




---
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.
---