When CoverageStores are created by setting the file via xml, the creation of the Coverage ignores the given name and uses nativeCoverageName instead.
This is because the name is not set after building the coverage, see here.
Something like the following should be enough to avoid this bug:
Before buildCoverage save coverage.getName() to some variable e.g. coverageName
After buildCoverage call coverage.setName(coverageName)
Steps to reproduce:
=> Results in 404
In your final POST (to create the coverage), why did you choose `<nativeName>` rather than `<nativeCoverageName>`? I'd like to ensure that I get the required documentation updates into this fix if possible, and understanding what information sources you used might help to make it more useful and relevant.
Sorry for my late reply. To be honest I don't even know whats the difference between nativeName and nativeCoverageName is.
Retest after rest-api-refresh merge