Exporting/Importing cluster configuration (templating)

[enzor]

I started playing around with paz, and i am finding very useful for some side projects i am working on.
One thing I am missing is the possibility to export the current cluster configuration in an external file , just to be able to reimport it later, instead of recreating everything anew via the UI.
The service should be available both from the UI and via API.
I will give it a try to implement it this weekend , so wish me luck!
Any tip in particular to where should i start from?

[enzor]

Possible user cases:

• creation of UATs
• easy creation/destroy of environment for saving money on AWS/DigitalOcean/etc
• Importing from other PaaS (admitted you know the import format)

[lukebond]

@enzor this is a great idea! i can see the benefits and it should be very easy to implement.

I will give it a try to implement it this weekend , so wish me luck!
good luck Enzo :)
YLD are doing a Paz Hackathon in Lisbon this weekend. join in the conversation, ask questions and share your work via our Gitter channel!

Any tip in particular to where should i start from?
yes, a few pointers:

• add any new REST endpoints here: https://github.com/paz-sh/paz-service-directory/blob/master/lib/routes.js (e.g. GET /services/export, POST /services/import or something)
• specify the schema for the import here: https://github.com/paz-sh/paz-service-directory/blob/master/resources/service/schema.js
• respond to the added routes here: https://github.com/paz-sh/paz-service-directory/blob/master/resources/service/controller.js
• the controller will call down to logic in the model here: https://github.com/paz-sh/paz-service-directory/blob/master/resources/service/model.js
• write tests for the new endpoints here: https://github.com/paz-sh/paz-service-directory/blob/master/test/test.js
• if those tests need fixtures, there is a dir for them and copy what the other tests do