-
Notifications
You must be signed in to change notification settings - Fork 2
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
DDA w/operator component cleanups and improvements #1251
Conversation
676da02
to
8355c2d
Compare
@@ -11,7 +11,7 @@ import ( | |||
) | |||
|
|||
// OperatorOutput is used to import the Operator component | |||
type OperatorOutput struct { | |||
type OperatorOutput struct { // nolint:revive, We want to keep the name as <Component>Output |
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.
What is the lint error?
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.
I was getting this lint error:
Error: components/datadog/operator/component.go:11:6: exported: type name will be used as operator.OperatorOutput by other packages, and that stutters; consider calling this Output (revive)
type OperatorOutput struct {
/merge |
Devflow running:
|
What does this PR do?
namespace
and operator image path inagentwithoperatorparams
andoperatorparams
KubernetesObjectRef
to the kubernetes componentKubernetesObjectRef
to the operator component outputWhich scenarios this will impact?
Motivation
Additional Notes