Now we just save an incoming YAML to a special DB field without any
validation or syncronization with DB models. If you send an empty file
we'll save it and will try to use it for deployment.


On Fri, Dec 20, 2013 at 2:59 AM, Andrew Woodward <[email protected]> wrote:

> ref: https://review.openstack.org/#/c/62495/
>
> The examples show only modifying only the network section, so I assumed i
> could upload just the network section. I used 'fuel --env 1 deployment
> --upload' but that caused the yaml to only contain uploaded data even
> though the other sections where not modified. is there a merge or overwrite
> style instead of replace?
>
> Andrew Woodward
> Mirantis
>
> --
> Mailing list: https://launchpad.net/~fuel-dev
> Post to     : [email protected]
> Unsubscribe : https://launchpad.net/~fuel-dev
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Andrey Danin
[email protected]
skype: gcon.monolake
-- 
Mailing list: https://launchpad.net/~fuel-dev
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~fuel-dev
More help   : https://help.launchpad.net/ListHelp

Reply via email to