Replies: 5 comments 9 replies
-
@PDumasBAR @l00mi What is your general opinion on this ? |
Beta Was this translation helpful? Give feedback.
-
Not sure if I missunderstand, but int.visualize.admin.ch does point to PROD Lindas, as documented here: https://gitlab.ldbar.ch/bafu/umweltdatenkiosk-planning#umgebungen So I assume you wanted to say test.visualize.admin.ch ? Nevertheless, the only real solution to this ever upcoming discussion is, that there is a (hidden) possibility to change the end-point in the client. (There should obviously be a default one, and it could be always PROD). Then the other two endpoints should be best selectable (drop-down). And finally it would be very use full to also allow a complete new end-point. I know that this will need you to also save the endpoint to each visualization, which is a bit of work. But I am pretty sure, that is the most robust and future proof solution, to this never ending discussion. |
Beta Was this translation helpful? Give feedback.
-
Yes my mistake 😊 Edited. Yes the selectable endpoint is related. We have planned to do this in the sprint. But even having the selectable endpoint is not the end of the story.
I do not think we had ever statuted on this one, and I am glad that we agree. While we will make it possible to change endpoints, I think we should make it as unfrequent as possible. For me, the best would be that this is disabled in production. @Rdataflow @pierredumas Would it sound possible to you ?
Why can't they use the draft feature for this ? |
Beta Was this translation helpful? Give feedback.
-
Thanks to awesome work @bprusinowski , we will now be able to select production database from test.visualize.admin.ch. I think this closes the discussion 🎉 |
Beta Was this translation helpful? Give feedback.
-
Simple and effective! 🥇 |
Beta Was this translation helpful? Give feedback.
-
These are my thoughts / questions on why we should not continue to use lindas-int for visualize-int.
Context
Users from BAFU primarily use int.lindas.admin.ch as their work tool as it is connected to lindas int.
Why having datasets on int feels like a bad idea
This is an assumption
When users have finished tweaking their dataset, they need to put it in production
They have to export / import their data from the cubes to “publish” a dataset from int to production
Then people have to recreate their charts inside the production environment
Users have to remember to sync the datasets from int to production, this sounds hard
The whole model would be simpler if charts could have a “visibility” setting.
Why do users use the int environment ?
Quotations are from @Rdataflow
What would be possible solutions ?
If there was a login, how would it impact this ?
How would user be able to use a custom endpoint to load their data ? Should they be allowed to ?
Personally I do not see the point on production.
Beta Was this translation helpful? Give feedback.
All reactions