You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The manage.py setup -G portion of scripts/load_configured_data fails on its first run in a clean environment because it tries to drop a GeoServer workspace that doesn't exist yet. purge_geoserver in config.py should only return False if the workspace exists and there was en error deleting it so that loading data into a new DistrictBuilder instance completes successfully.
[this should explain why the current behaviour is a problem and why the expected output is a better solution.]
Note: Please check first before submitting so that we do not have to handle and close duplicates!
Problem description
The
manage.py setup -Gportion ofscripts/load_configured_datafails on its first run in a clean environment because it tries to drop a GeoServer workspace that doesn't exist yet.purge_geoserverinconfig.pyshould only returnFalseif the workspace exists and there was en error deleting it so that loading data into a new DistrictBuilder instance completes successfully.[this should explain why the current behaviour is a problem and why the expected output is a better solution.]
Note: Please check first before submitting so that we do not have to handle and close duplicates!
Replication Steps
scripts/updatescripts/load_configured_dataExpected Behavior or Output
scripts/load_configured_datacompletes successfully