brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bernd Clemenz <bernd.clem...@gmail.com>
Subject Re: Adding children to an application via API fails
Date Wed, 22 Jul 2015 13:54:07 GMT
Hi Svetoslav,

thanks for your quick answer. Setting the right Conent-type header did the
trick! For my application, which automates Brooklyn, this was a solution.
The captured HTTP traffic from the Brooklyn shows, it's using :
'Content-Type: application/x-www-form-urlencoded; charset=UTF-8'. The
requst from the UI fails. So, we may see here bug.

Regards and Thanks
Bernd


2015-07-22 14:41 GMT+02:00 Svetoslav Neykov <
svetoslav.neykov@cloudsoftcorp.com>:

> Hi Bernd,
>
> You can use the following curl:
> curl -T blueprint-file.bom -X POST
> http://localhost:8081/v1/applications/m4mbJLeW/entities/uc4GJdO9/children?start=true&timeout=20ms
> <
> http://localhost:8081/v1/applications/m4mbJLeW/entities/uc4GJdO9/children?start=true&timeout=20ms
> >
>
> or add to your existing command:
> -H "Content-type: application/yaml"
>
> Svet.
>
>
> > On 22.07.2015 г., at 15:13, Bernd Clemenz <bernd.clemenz@gmail.com>
> wrote:
> >
> > Hi,
> >
> > I'm trying to add children to an application in Brooklyn
> (0.7.0-SNAPSHOT).
> > The URL used is
> >
> >
> /v1/applications/m4mbJLeW/entities/uc4GJdO9/children?start=true&timeout=20ms
> >
> >
> > The request always fails with an HTTP 415 status code (unsupported media
> > type). This happens always, no matter of what the 'childrenSpec' content
> is.
> >
> > If this is used by anyone, I would be glad to see some working YAML
> > example, or just the formal structure.
> >
> > Thanks,
> > Bernd
>
>
> --
> 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.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message