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

Datashader instance driven by configuration, not user set / saved object captured #28

Open
ndmitch311 opened this issue Mar 30, 2022 · 0 comments

Comments

@ndmitch311
Copy link
Contributor

Currently when a user creates a Datashader layer it is prepopulated with a URL that is set in configuration , but can be modified by the user. The instance of Datashader used on a Map/Dashboard should always be the one that points to the same Elasticsearch as the Kibana instance because it is within the Datashader configuration that the ES instance utilized is defined, not based on the Kibana used.

ENHANCEMENTS:
-Change Kibana UI so URL is not user editable.
-Change Map Component/Dashboard save so URL is not captured in SavedObjects, but rather read from config when the MapDashboard is utilized.

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

No branches or pull requests

1 participant