Importing a configuration fails for distributed configurations using the REST API

Description

The REST API endpoint to import a configuration fails if you want to import a distributed configuration on the Slave side.

Steps to reproduce

  1. Export Master + Slave using REST

  2. Import Master Config using REST

Expected result

Import is working and user can publish draft on Master side, so that Slave can update it.

Actual result

REST API returns an error as soon as you try to import a configuration.

Environment

None

Assignee

Unassigned

Reporter

Sync User [K15t]

Labels

None

Participants

None

QA Status

None

Deployment

Server

Documentation Status

None

UI Concept

None

External Votes

None

Components

Fix versions

Affects versions

Priority

Major
Configure