Github user neykov commented on a diff in the pull request:
https://github.com/apache/brooklyn-server/pull/612#discussion_r108640433
--- Diff:
camp/camp-brooklyn/src/main/java/org/apache/brooklyn/camp/brooklyn/spi/creation/BrooklynComponentTemplateResolver.java
---
@@ -257,6 +257,7 @@ public boolean canResolve() {
new
BrooklynEntityDecorationResolver.EnricherSpecResolver(yamlLoader).decorate(spec,
attrs, encounteredRegisteredTypeIds);
new
BrooklynEntityDecorationResolver.InitializerResolver(yamlLoader).decorate(spec,
attrs, encounteredRegisteredTypeIds);
new
BrooklynEntityDecorationResolver.SpecParameterResolver(yamlLoader).decorate(spec,
attrs, encounteredRegisteredTypeIds);
+ new
BrooklynEntityDecorationResolver.TagsResolver(yamlLoader).decorate(spec, attrs,
encounteredRegisteredTypeIds);
--- End diff --
@tbouron is onto something here. For example for effectors we go through an
initializer and try not to expand the keywords too much.
I think that anything that is a "first class concept" on an `EntitySpec`
should have the corresponding way to express in yaml. There are tags on specs,
so `brooklyn.tags` in CAMP makes sense. Similarly for `brooklyn.parameters`,
`brooklyn.config`. There are no effectors on the `EntitySpec` so there are no
`brooklyn.effectors` in CAMP.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
