Closed MeltyBot closed 1 year ago
This has been marked as stale because it is unassigned, and has not had recent activity. It will be closed after 21 days if no further activity occurs. If this should never go stale, please add the evergreen
label, or request that it be added.
Migrated from GitLab: https://gitlab.com/meltano/sdk/-/issues/349
Originally created by @aphethean on 2022-03-16 15:32:32
Summary
Add a property to plugin settings configuration called 'hidden' and deprecate kind=hidden
Proposed benefits
Once available, deployments of the taps/targets/other plugins will be able to hide settings from users and store them securely when necessary.
Proposal details
When building a dynamic UI on top of the plugin settings, we've found that kind=hidden is incompatible with kind=password
As a example, kind=password means the setting is stored encrypted. Whereas, kind=hidden only means that the setting should not be displayed.
The following permutations are necessary:
hidden
Setting FieldThe
hidden
setting field should define the conditions under which the setting is visible for configuration by the user.true
, the setting should be hidden from the userfalse
, the setting should be shown to the user (optional)Example
oauth_credentials.access_token
SettingConfiguration for an
oauth_credentials.access_token
setting should be both hidden from the user, and stored encrypted.In this case we need
oauth_credentials.scope
SettingConfiguration for an
oauth_credentials.scope
setting is not sensitive, but does not need to be shown to the user for configuration.In this case we need
tap-googleads
ExampleBest reasons not to build
Deprecation proposed in this feature will eventually mean a migration for users of kind=hidden