Our use case : update of a layer which has previously been publish by the hand BUT the datastore are not the same. The workspace is the same.
- on the source GS : the layer is published in a datastore named "espace_public_update"
- on the target GS : the datastore is named "espace_public"
This situation is "normal" because on our public georchestra we do not allow layer update.
As maelstro could not find the target datastore as identical to the source datastore, it produces a 404 error.
This 404 error must appear on the frontend UI to clearly inform the publisher.
Our use case : update of a layer which has previously been publish by the hand BUT the datastore are not the same. The workspace is the same.
This situation is "normal" because on our public georchestra we do not allow layer update.
As maelstro could not find the target datastore as identical to the source datastore, it produces a 404 error.
This 404 error must appear on the frontend UI to clearly inform the publisher.