Now that versioning is deprecated, how do we migrate environments?

Hey guys,

I might be miss understanding something here, or maybe I missed something in the documentation, but now that you’ve deprecated version support with back endless 4.0, how do we achieve this : http://support.backendless.com/knowledge-base/article/migrating-apps-backend-from-one-environment-to-the-other-one

  • Terry

Hi Terry,

The same is now accomplished via export/import functionality: you can do that with settings, data and files.

ok, so now it’s a multi part manual step, is there a way I can automated this? I don’t want to be doing this by hand for every release, I don’t know if user feedback is important to you guys and don’t get me wrong, you’ve added some nice features recently, but IMO this is a huge step backwards for something that should be simple.

It’s actually not that longer than it was it 3.x with deploying version: you still can check everything (settings, data, files) when doing export, and then just import the resulting archive in a new app.

This is great, I just don’t want to do it manually. Is there a way to automate this, I’d love to wrap it up in my deploy process so I didn’t have to do it by hand.

There was no automated way to do that in 3.x, as I remember, and so there’s no such in 4.x. You may try to imitate this with a custom shell script, using console management api.

if there is a place to make a feature request, I’d love to do it, at the moment, I’ve managed to automate every single piece of my deploy process, I’m just being held back by backendless.

You can create a new topic in ‘Ideas’.

Have done here : http://support.backendless.com/t/automate-the-promotion-of-environments

Thanks.