Endpoint Configuration Resets to Default after Redeployment

[exalate-issue-sync]

Describe the bug :

Changes to an individual endpoint, whether it's an http header, idle timeout, etc, are reset to the default values after making other API changes and redeploying.

To Reproduce :

Steps to reproduce the behaviour:

1. On a v2 API, edit an endpoint and disable the 'Inherit Configuration'.
2. Add an HTTP header, then save and deploy the API.
3. Verify that the HTTP header that was added is still present after deploying the API.
4. Modify another component of the API (eg. add a new policy, update the description, etc) and redeploy the API.
5. Go back to the endpoint's Configuration. The header no longer exists.
6. This behavior applies to any other configuration changes as well. For example, if changing the idle timeout to 30000 ms and then following the same steps, the configuration will revert back to the default 60000 ms after redeployment.
7. The configuration for endpoint groups is not affected by this, and all modifications remain intact after multiple redeployments.

Expected behaviour :

Individual endpoint configuration, once saved and deployed, should be retained through all succeeding API changes and redeployments

Current behaviour :

Individual endpoint modifications are removed when other parts of the API are updated and then redeployed.

Desktop :

• Environment: 4.1.0

_{* Please see Zendesk Support tab for further comments and attachments.}

[exalate-issue-sync]

This issue has been fixed in versions 4.0.11, 4.2.0, 4.1.2