Hot-reloading tasks in spaces

[dgudkov]

@reynsnivea

create a git repo in the easymorph server space where the task XML-files reside. Does the .git folder create problems for task execution ?

That shouldn't be a problem. It if becomes a problem, we'll fix that.

@reynsnivea

How can we also automate the overwrite of parameter values. For example we have a database parameter that we have to overwrite in the production environment. We also have a lot of other params that we have to overwrite when moving to prod. So my question: when we pull a new version of the tasks with git, it will have the param values from dev and we would like to automatically overwrite them with the prod values.
One idea that comes to my mind is that we could create 1 parameter ‘environment’ and all other parameters are calculated parameters that change as a function of the parameter ‘environment’. When we want to apply this to our current tasks, we have to change all our parameters to calculated params. So that’s quite a workload…
Any suggestions ?

If you need to specify environment-specific variables via parameters, consider using the "Shared memory" instead of task parameters. The Shared Memory is a more appropriate place to store environment-specific settings.