search

appsmithorg / appsmith

Platform to build admin panels, internal tools, and dashboards. Integrates with 25+ databases and any API.
https://www.appsmith.com
Apache License 2.0
34.51k stars 3.72k forks source link

[Feature]: Enable sharing of credentials of individual datasources when forking an app (instead off all datasources or none) #16577

Open GreenFlux opened 2 years ago

GreenFlux commented 2 years ago

Is there an existing issue for this?

Summary

The template datasource share flag (for reconnect datasource modal) is app-wide. There is no option to only share credentials for certain datasources and remove others when forking. We often want to use the mock_user (or other Postgres) table with an API, SaaS connector or SMTP connection that we do not want to share.

Why should this be worked on?

For now, we have to not-share all credentials, making it that much more difficult for a user to reconfigure the app to a runnable state after forking. We should be able to safely share the credentials for our mock databases while still removing credentials for 3rd party APIs, SaaS connectors, etc. This will improve the forking experience for our users and enable us to build more complex templates.

Nikhil-Nandagopal commented 2 years ago

Rather than an in-app experience, I am assuming we should just have a backend way of enabling this since this isn't so much a user need as our own internal need

GreenFlux commented 2 years ago

@Nikhil-Nandagopal , yes, for now this just an internal need, and only for templates. We may need it for community contributed modules though if we build a market place in the future. But I don't think we need any frontend changes for now.