Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Deprecate --export flag from get command #73787
What type of PR is this?
What this PR does / why we need it:
Does this PR introduce a user-facing change?:
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: soltysh
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
referenced this pull request
Feb 7, 2019
The bugs are secondary. The primary issue is that there are multiple conflicting goals and use cases for this feature that require opposite behavior. Some require dropping cluster-specific info, some require preserving it.
I don't think the current approach to export is consistent or general enough to promote.
Before deprecating could we have a documented alternative.
End users are already facing the deprecation of
Any object can certainly be cleaned up by hand without too much hassle but
Since the issues mentioned as justification go back 2016, might as well solve it first once and for all before deprecating this.