Introduction
Currently policy-participant dons not support more than one instance due the policy type and policy saved into service template. For same reason there are specific implementations that involves ACM-runtime and intermediary to support policy-participant:
- At deployment action ACM-Runtime fetches policy type and policy from service template and add them into the deploy message
- Intermediary saves in memory policy type and policy from deploy message to be available in any in subsequent instance actions
Service template and instance
...
- In "policy/docker" insert the policy type and policy into the instance. That submit will be backward compatible
- Make the policy-participant changes in ACM. That submit will work due the changes done before
- In "policy/docker" remove the policy type and policy from the service template. That submit will be OK due the policy-participant updateupdated
Regression test
Replace service template and instance:
...