Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wondering why using get_geoserver_cascading_workspace #222

Closed
pchevali opened this issue Feb 5, 2024 · 2 comments · Fixed by #225
Closed

Wondering why using get_geoserver_cascading_workspace #222

pchevali opened this issue Feb 5, 2024 · 2 comments · Fixed by #225

Comments

@pchevali
Copy link
Contributor

pchevali commented Feb 5, 2024

Hi,

In the importer plugin there are lots of references to "get_geoserver_cascading_workspace", however this geoserver workspace seems to be dedicated to remote services as far I understand.

Is there a reason to return the value of CASCADE_WORKSPACE instead of DEFAULT_WORKSPACE here ?

Thanks

@mattiagiupponi
Copy link
Contributor

Hi, it was used mainly because 99% of the time is the same workspace and for the "create=True" option. But yes, i guess is worth to change it and use the DEFAULT WORKSPACE

@mattiagiupponi
Copy link
Contributor

Code updated, will be used from the new versions of the importer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants