-
Notifications
You must be signed in to change notification settings - Fork 11.6k
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
Plugins: Remove secure socks proxy feature toggle #66611
Conversation
(Open the links below in a new tab to go to the correct steps)
|
Backend code coverage report for PR #66611
|
Frontend code coverage report for PR #66611
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with some questions/comments
public/app/plugins/datasource/graphite/configuration/ConfigEditor.tsx
Outdated
Show resolved
Hide resolved
@@ -308,6 +310,7 @@ export const DataSourceHttpSettings = (props: HttpSettingsProps) => { | |||
<CustomHeadersSettings dataSourceConfig={dataSourceConfig} onChange={onChange} /> | |||
)} | |||
</> | |||
{secureSocksDSProxyEnabled && <SecureSocksProxySettings options={dataSourceConfig} onOptionsChange={onChange} />} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In regards to external plugins there's possibly a problem I see with this approach, but maybe external plugins is not a concern for now? If a plugin author would provide secureSocksDSProxyEnabled=true
to the DataSourceHttpSettings component it would always render even if the secure socks configuration is not enabled in Grafana config, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct ☝🏻 But I don't think this is a blocker. We should probably try to break this UI into smaller components in the future which might mitigate this problem.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
@@ -308,6 +310,7 @@ export const DataSourceHttpSettings = (props: HttpSettingsProps) => { | |||
<CustomHeadersSettings dataSourceConfig={dataSourceConfig} onChange={onChange} /> | |||
)} | |||
</> | |||
{secureSocksDSProxyEnabled && <SecureSocksProxySettings options={dataSourceConfig} onOptionsChange={onChange} />} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct ☝🏻 But I don't think this is a blocker. We should probably try to break this UI into smaller components in the future which might mitigate this problem.
What is this feature?
This PR removes the feature toggle
secureSocksDSProxyEnabled
, which was added in this PR. This will still not be enabled unless it is enabled in the config.ini, viasecure_socks_datasource_proxy.enabled
.It also cleans up repeated UI code by moving the toggle to the
DataSourceHttpSettings
, if the feature is enabled on the instance. This is not available for the alertmanager, so it is false for that datasource.Which issue(s) does this PR fix?:
Fixes https://github.com/grafana/hosted-grafana/issues/3764
Special notes for your reviewer: