Do not add protobuf serializer to accepted content-types #59
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is a
What this PR does / why we need it:
Quick hack to prevent https://bugzilla.redhat.com/show_bug.cgi?id=1768820 , where namespaces couldn't terminate because the new metadata client used in 1.16 for namespace deletion requests both protobuf and JSON. Protobuf was listed as an accepted content type by the service catalog, but there are no protobuf serializers for the service catalog types, so it would just fail whenever the namespace deleter made those requests. This PR just stops the protobuf serializer from being added at all, which means the service catalog should properly fall back to JSON
Which issue(s) this PR fixes
Fixes #
Please leave this checklist in the PR comment so that maintainers can ensure a good PR.
Merge Checklist:
breaking the chart release and existing clients who provide a
flag that will get an error when they try to update