Github user aledsage commented on the issue:
https://github.com/apache/brooklyn-docs/pull/182
At the risk of making more work for us @tbouron, perhaps we should split
this PR into three parts (where 1 and 2 could be done together):
1. change example structure to be consistent (e.g. always using
`brooklyn.config`).
2. change examples that use a bad-looking alias, where the alternative
"real name" would make that particular example look cleaner/simpler.
3. after we support deprecation and we've changed each name to be the
"best" name, we update the examples to use those authoritative names.
What I want to avoid is us temporarily changing the docs such that the
examples look more complicated, in ways that we end up changing back again in
not very long.
---
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.
---
