Skip to content
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 managedFields from display of Pod resource and events #2554

Merged
merged 1 commit into from
Nov 1, 2022

Conversation

AlanGreene
Copy link
Member

Changes

managedFields clutters up the output and is not particularly useful to users of the Dashboard. Filter this out when displaying the Pod resource and associated events so users can focus on the more useful content provided in the other fields.

This filtering is already done on the ResourceDetails pages when in the YAML view for a single resource. Updating TaskRun details for consistency.

/kind misc

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

  • Docs included if any changes are user facing
  • Tests included if any functionality added or changed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including
    functionality, content, code)
  • Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
  • Release notes block below has been updated with any user facing changes (new features, significant UI changes, API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
  • Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

Filter out managedFields when displaying Pod resource and event details on the PipelineRun and TaskRun pages.

@tekton-robot tekton-robot added kind/misc Categorizes issue or PR as a miscellaneuous one. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Oct 27, 2022
@AlanGreene AlanGreene removed the request for review from skaegi October 27, 2022 14:33
Copy link
Contributor

@briangleeson briangleeson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be worth having a test that includes managedFields data, and verifying that it is removed as expected?

`managedFields` clutters up the output and is not particularly useful
to users of the Dashboard. Filter this out when displaying the Pod
resource and associated events so users can focus on the more useful
content provided in the other fields.

This filtering is already done on the ResourceDetails pages when
in the YAML view for a single resource. Updating TaskRun details
for consistency.
@AlanGreene
Copy link
Member Author

AlanGreene commented Nov 1, 2022

Updated test to ensure managedFields is not displayed 👍 Thanks

Copy link
Contributor

@briangleeson briangleeson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@tekton-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: briangleeson

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Nov 1, 2022
@tekton-robot tekton-robot merged commit f9e5319 into tektoncd:main Nov 1, 2022
@AlanGreene AlanGreene deleted the managedFields branch November 1, 2022 11:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/misc Categorizes issue or PR as a miscellaneuous one. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants