-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[chore][internal/k8stest] Make k8stest package publicly available #36661
Conversation
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.
Looks good on the Datadog side.
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'd like to continue discussing this proposal in the issue. Making things public puts a burden on maintaining.
Sure, let's discuss. I opened this PR just to visualize what I am proposing. |
8df0b90
to
b0cb0cd
Compare
0c31374
to
43cf2de
Compare
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
not stale |
fc687df
to
129c5e9
Compare
129c5e9
to
66fee7a
Compare
unblocking based on discussion in issue
66fee7a
to
74dc5fe
Compare
b4da7b2
to
a4c2989
Compare
a4c2989
to
aa94ee3
Compare
15b2a9c
to
db0e6a5
Compare
Signed-off-by: odubajDT <[email protected]>
db0e6a5
to
3baafc0
Compare
@andrzej-stencel would you be willing to merge this as well? Thank you! |
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 see there are some functional changes to the CreateCollectorObjects
method. Ideally they should be done in a separate pull request, but I'm willing to let this pass. Probably better to introduce the breaking changes before the module is public, even if there are no stability guarantees on it.
Description
Link to tracking issue
Part of #36615