-
Notifications
You must be signed in to change notification settings - Fork 268
-
|
Original issue by @devendrakhatri: openblocks-dev/openblocks#297 For the use cases where we have multiple environments (DEV, UAT, PROD) and each environment has a dedicated database with exactly same schema. Can we think of passing datasource dynamically? Probably we can call it "environment manager" which can manage all the base URLs, database,. etc. at single place and dashboard can switch to environments using dropdown list?
|
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 3
Replies: 3 comments 6 replies
-
FYI moving feature request into a discussion as this needs a bit more thought first.
I would not recommend Lowcoder connecting to multiple environments as this can lead to editing production data by accident. Why not having different instances of Lowcoder for each environment?
Beta Was this translation helpful? Give feedback.
All reactions
-
Without this feature, we need to edit applications for each stack and it is not guaranteed to have same applications across the environments because it is done by humans at the moment.
Beta Was this translation helpful? Give feedback.
All reactions
-
Anyway, we need a solution to reuse the application code for each environment.
Beta Was this translation helpful? Give feedback.
All reactions
-
How many queries from a single data source do you have per app?
Beta Was this translation helpful? Give feedback.
All reactions
-
Beta Was this translation helpful? Give feedback.
All reactions
-
What you can do as a temporary workaround (albeit painful) is:
- Create option element that will be your environment switcher.
- Duplicate queries by the number of environments you have
- Create a transformer that will run a query based on the environment selected
Your request basically describes having dynamic data sources if I understand that correctly.
Beta Was this translation helpful? Give feedback.
All reactions
-
It's been awhile since there was any traffic on this particular discussion, but I'd like to chime in with some additional use cases.
- I've got lots of job servers, each with its own database that both controls the jobs that run on that server and which logs the results and output of each job. I'd like to have a single app that allows the user to pick a server from a drop-down menu and then query the database on that server (using just one query) for the job(s) status(es).
- Similar, but let's say with a web api: I've got several controllers for building automation, each with its own REST API endpoint. I'd like to allow a user to pick the controller (building, perhaps), and then view the output from the REST query when run against that particular server
- I'd like to give users the ability to start the same stored procedure on seveal different database instances; let's say they are three non-production servers: dev, stage, and test. This stored procedure might be involved in change management for code deployment, or to run a set of unit tests on migrated code
If it were possible to use {{ placeholder }} values in connection strings as well as in queries, that would be pretty great.
Beta Was this translation helpful? Give feedback.
All reactions
-
Another use case for dynamic data sources is connecting to the same data source, but using different database connection authentication (username/pwd) based on the user currently using LowCoder.
Beta Was this translation helpful? Give feedback.
All reactions
-
Environments will be supported in the Lowcoder EE Version.
Now... Since quite a while we mention the EE Version and still not even show up with a v0.1.alpha of it.
Reason is, that we focus much to the Community Edition to make it "best in place".
However, we do still have development ongoing for EE version and somewhen in Summer we should finally show up with it.
Environments will be part of it.
Beta Was this translation helpful? Give feedback.