All workloads being updated must be running to the same Application
All configurations sent will be applied to all workloads
All resources running in the workloads must be sent in the request. The API will distribute them to the corresponding workloads they’re in
Some Internal Improvements
Deployment of Applications/Workloads now has a new validation being performed in the API
Only one workload in the platform can be producing output data for a Resource/Datastream
When a workload is deployed, we identify the Resource/Datastream pairs that will be owned/produced by it
What determines if a resource/datastream is owned by a workload is the value of way
If way is output, input-cc or input-cc+output, it means it’s owned by the workload
If, when deploying a workload, a resource/datastream is sent as an owned resource and this resource is already owned by another workload, the API will through an error saying the resource context is already locked!
The Deployment of Applications/Workloads will now use App defaults to fill some fields in the workload if these fields were not sent in the request
The fields being automatically filled, if not sent, are the following:
runtime.resources[*].datastreams , filled with information from App Version io and, if set, with defaults.app.io_datastream_mapping
runtime.configuration , filled with information from App Version defaults.app.configuration
system , filled with information from App Version defaults.system
deployment.deployment_type , filled with information from App Version defaults.deployment.deployment_type
deployment.max_resources , filled with information from App Version defaults.deployment.max_resources
deployment.target , filled with information from App Version defaults.deployment.target