Skip to content

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

Closed
tbouron wants to merge 1 commit intoapache:masterfrom
tbouron:fix/priority-vs-pinned
Closed

Config keys and parameters can now be marked as "pinned"#354
tbouron wants to merge 1 commit intoapache:masterfrom
tbouron:fix/priority-vs-pinned

Conversation

@tbouron
Copy link
Copy Markdown
Member

@tbouron tbouron commented Sep 27, 2016

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)

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

@tbouron
Copy link
Copy Markdown
Member Author

tbouron commented Sep 29, 2016

Close this in favor of #358

@tbouron tbouron closed this Sep 29, 2016
@tbouron tbouron deleted the fix/priority-vs-pinned branch September 29, 2016 14:49
asfgit pushed a commit that referenced this pull request Sep 30, 2016
Allow REST API to return the pinned config key and their constraints for catalog apps

Based on #354

This expose a new `pinned` flag and `constraints` key to the REST API. It allows the following:
- 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](6f624c7#diff-5310fbeb1f42a3a4cf0508ea441440baL82))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant