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
Spatial Dataset Service created w/ CLI does not work until manually saved in admin pages #763
Labels
Comments
The tethys/tethys_cli/services_commands.py Line 197 in 6266f2c
It needs to assign values as is done here: tethys/tethys_services/models.py Line 135 in 6266f2c
|
Merged
Merged
swainn
added a commit
to swainn/tethys
that referenced
this issue
Oct 8, 2022
* Fix for Spatial Dataset Service created w/ CLI does not work until manually saved in admin pages tethysplatform#763 * Fix lint
swainn
added a commit
to swainn/tethys
that referenced
this issue
Oct 8, 2022
* Fix for Spatial Dataset Service created w/ CLI does not work until manually saved in admin pages tethysplatform#763 * Fix lint
swainn
added a commit
to swainn/tethys
that referenced
this issue
Oct 8, 2022
* Fix for Spatial Dataset Service created w/ CLI does not work until manually saved in admin pages tethysplatform#763 * Fix lint
swainn
added a commit
to swainn/tethys
that referenced
this issue
Oct 8, 2022
* Fix for Spatial Dataset Service created w/ CLI does not work until manually saved in admin pages tethysplatform#763 * Fix lint
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tethys Version: 3.4.1
If the
tethys services create
command is used to create a spatial dataset service like so:attempting to retrieve the engine returns
None
, which can result in errors like the following:However, this can be fixed by opening the Spatial Dataset Service in the admin pages and saving it again.
tethys services create
seems to be missing some important step.This issue can be reproduced using the following docker-compose: https://github.com/Aquaveo/tethys_portal_docker_sirba
The text was updated successfully, but these errors were encountered: