Conflict errors should be handled gracefully while a registration or provider is being created. In case of conflict the conflicting registration id or providerId should be fetched from the exception response header and used to update that registration or provider
Expected Behaviour
Conflict errors should be handled gracefully while a registration or provider is being created. In case of conflict the conflicting registration id or providerId should be fetched from the exception response header and used to update that registration or provider
See jira issue https://jira.corp.adobe.com/browse/CI-6365
Actual Behaviour
Conflict Exception is thrown and api terminates without further processing
Reproduce Scenario (including but not limited to)
Steps to Reproduce
Platform and Version
Sample Code that illustrates the problem
Logs taken while reproducing problem