Github user ahgittin commented on the pull request:
https://github.com/apache/incubator-brooklyn/pull/865#issuecomment-135149286
There is a Brooklyn camp yaml reference on the website. Most useful thin
would be autocomplete for catalog item types and their configuration keys
both of which are exposed through rest api.
On 26 Aug 2015 19:15, "Alexandru Zbarcea" <[email protected]> wrote:
> @ahgittin <https://github.com/ahgittin> - I will take a look to the bug.
> Also keep in mind that is not integrated in all the views, neither the
> *events* aren't propagated.
>
> @tbouron <https://github.com/tbouron>, is there a documentation for the
> CAMP syntax/semantics (for hint) besides the spec
> <http://docs.oasis-open.org/camp/camp-spec/v1.1/camp-spec-v1.1.html>?
>
> â
> Reply to this email directly or view it on GitHub
>
<https://github.com/apache/incubator-brooklyn/pull/865#issuecomment-135128315>
> .
>
--
Cloudsoft Corporation Limited, Registered in Scotland No: SC349230.
Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP
This e-mail message is confidential and for use by the addressee only. If
the message is received by anyone other than the addressee, please return
the message to the sender by replying to it and then delete the message
from your computer. Internet e-mails are not necessarily secure. Cloudsoft
Corporation Limited does not accept responsibility for changes made to this
message after it was sent.
Whilst all reasonable care has been taken to avoid the transmission of
viruses, it is the responsibility of the recipient to ensure that the
onward transmission, opening or use of this message and any attachments
will not adversely affect its systems or data. No responsibility is
accepted by Cloudsoft Corporation Limited in this regard and the recipient
should carry out such virus and other checks as it considers appropriate.
---
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.
---
