-
Notifications
You must be signed in to change notification settings - Fork 174
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
remove k8s.container.status.current_waiting_reason resource attribute #1115
remove k8s.container.status.current_waiting_reason resource attribute #1115
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.
Please re-generate the markdown tables.
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.
Note: attribute definitions are not related to a signal. I.e. this attribute can still be used, just not as a resource attribute.
If the only use case for it was to be used as a resource attribute, then yes, it's best to remove it before it was released and re-introduce if it's ever needed.
a609a74
to
99284a1
Compare
Reverts #997 due to immutability constraint.
Ref #997