Variable migrations

OttoFMS
1

Does OttoFMS offer support for the following?:

All on the same server, I have my master dev file and the (say) 30 files that are versions of the dev file. I’d like to be able to build a filemaker file that has a list of these 30 files and update those files (migrate the schema from the dev file to the selected files).

I’d have to pass ottoFMS some sort of variable about the filename I’d like to migrate the dev file schema into. Does OttoFMS support something like this?

2

Hey Matt,

Deployments themselves are not variable, so you can’t give it a pattern to deploy files against or something similar. However, you can programmatically create deployments with OttoFMS.

You could build the Deployment JSON dynamically to support this. Deployments are just a large JSON object that gets sent to the destination server via API, so you could build and send the JSON in FileMaker using the list of files you want to migrate to. You just need to specify the same source file for all of the destination files you’d like to send to. You can see examples of the JSON in OttoDeploy by clicking the “Copy Deployment JSON” button in the top right of any deployment.

Does that answer your question?

-Kyle

3

I’ll also call out that OttoDeploy supports this natively (if you don’t want to change the list of files programmatically). You can specify multiple target files from the same source file, which I think would fit your use case here. If you just want to do that then you could specify the list of files from the same source and then just toggle on and off the files you want to send with the deployment.

-Kyle

4

Thanks @kduval I believe that does answer my question. When you say:

“Deployments are just a large JSON object that gets sent to the destination server via API, so you could build and send the JSON in FileMaker using the list of files you want to migrate to”

Do you have any documentation about this process I could look at on how to pass this json object up to the server?

5

Hey Matt,

You can find the API Doc here (or in the help menu in the OttoFMS console). The endpoint you’re looking for the the “Start a Deployment” endpoint. The JSON is quite complex, I’d recommend building the main parts with OttoDeploy, then manipulating the fileOperations key in your subdeployment to change the file list.

-Kyle