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

Flag --export has been deprecated and is now removed in oc 4.6 #229

Closed
michaelsauter opened this issue Oct 30, 2020 · 2 comments · Fixed by #230
Closed

Flag --export has been deprecated and is now removed in oc 4.6 #229

michaelsauter opened this issue Oct 30, 2020 · 2 comments · Fixed by #230
Assignees
Labels
bug Something isn't working

Comments

@michaelsauter
Copy link
Member

michaelsauter commented Oct 30, 2020

See e.g. https://www.reddit.com/r/openshift/comments/fyms4k/flag_export_has_been_deprecated/ and kubernetes/website#14432.

The flag has been removed in openshift-clients-4.6.0-202006250705, even though I can't really find how that change was introduced, probably by a bump of k8s. There is no mention whatsoever in any release notes I can find. OpenShift 4.6 has been released three days ago: https://www.openshift.com/blog/red-hat-openshift-4.6-is-now-available.

Looks like we need to use plain get and implement the --export functionality ourselves. I think we already do this partially, but there could be some nasty details.

@michaelsauter michaelsauter added the bug Something isn't working label Oct 30, 2020
@michaelsauter michaelsauter self-assigned this Oct 30, 2020
@michaelsauter
Copy link
Member Author

michaelsauter commented Oct 30, 2020

Update no.1: I ran make test without --export against an OpenShift 3.11 cluster and it passes. However, the E2E tests do not cover all supported resources right now so I would take it with a grain of salt.

@michaelsauter
Copy link
Member Author

michaelsauter commented Oct 30, 2020

Update no.2: Looking at https://github.com/opendevstack/tailor/blob/master/pkg/openshift/item.go#L18-L39, it looks like we handle all fields that are outside /spec already that should be excluded. So we'd only need to clean up if --export removed some field under /spec that would now be shown.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant