Require a RESTful api to deploy policy files

This requirement has been evaluated. Looking at current plans, it is not likely that this would be implemented in future zOS Connect EE releases, so correspondingly this requirement is being rejected.

Whilst the requirement to deploy policy files into a production environment is valid, the lack of votes from the community suggests that production deployment of policies can be achieved today through the used of typical DevOps best practices. eg:
- Policies should be placed under source control
- Policy files can be validated against the published policy schema as part of a DevOps pipeline.
- Test servers (along with automated tests) can validate schema file content before they it hit production.
- Deployment automation can ensure that only the intended polices (or resources) are changed
- When the REFRESH command is used only changed policies (or resources) are updated
- Blue/Green deployment can be used to ensure no disruption to workload

Policy files can change the behaviour of an entire server so we would recommend that significant server changes like this are deployed into production using the techniques above. DevOps practices like these also provide the benefit of ensuring a repeatable, auditable and consistent change process and can be used across your entire enterprise to drive confidence and agility.

Additional comment and context by initial raiser:
_______________________________________

The requirement here is a refresh process that:
- Makes changes to just the policy file and can be performed when the server is running at high volume with no downtime/API failure.
- The above process should only implement a valid policy file and not implement an invalid policy file. Feedback information should also be provided as to the actual success or failure of the policy refresh.

In addition to the functional advantages provided by the above - meeting this requirement will give the needed flexibility to implement the policy file in different ways.