Strategies

This page describes the different strategies the plugin offers.

Strategy types

The following strategy types exist.

Not every strategy is supported for every orchestrator. See the following tables for more details:

Strategy	Supported	Description
`UPDATE`	Yes	Every resource in your configuration file will be created, if it doesn’t exist in the cloud already. If it already exists in the cloud, it will be updated according to your configuration file using Marathon’s default update mechanism. All existing resources in the cloud, which are not mentioned in your configuration file stay untouched.
`REPLACE`	Yes	Every resource in your configuration file will be created, if it doesn’t exist in the cloud already. If it already exists in the cloud, it will be replaced according to your configuration file using Marathon’s default replace mechanism. All existing resources in the cloud, which are not mentioned in your configuration file stay untouched.
`RESET`	No	Not supported. This strategy is only available in Kubernetes clouds.

Strategy	Supported	Description
`UPDATE`	Yes	Every resource in your configuration file will be created, if it doesn’t exist in the cloud already. If it already exists in the cloud, it will be updated according to your configuration file using the default Kubernetes update mechanism. All existing resources in the cloud, which are not mentioned in your configuration file stay untouched. ATTENTION: This strategy is not supported for ReplicationControllers and Pods (use Deployments instead)!
`REPLACE`	Yes	Every resource in your configuration file will be created, if it doesn’t exist in the cloud already. If it already exists in the cloud, it will be replaced according to your configuration file using the default Kubernetes replace mechanism. All existing resources in the cloud, which are not mentioned in your configuration file stay untouched.
`RESET`	Yes	If the namespace specified in the EnvironmentExtension exists in the cloud, it will be deleted (including all resources it contains). Afterwards the namespace will be recreated and all resources within your configuration file are deployed. If the namespace doesn’t exist in the cloud, it will be created and all resources within your configuration file are deployed.