Fixes #36545 - Correcting apidoc for reclaim_space endpoint of smart-… #10630
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.
What are the changes introduced in this pull request?
Modification of APIDOC to include the right reclaim_space endpoint for external smart-proxies
Considerations taken when implementing this change?
When we invoke the "Reclaim Space" action from WebUI for any external smart-proxies, that triggers the right API call as expected.
But navigating to the API doc, we can see reclaim_space endpoint is not mentioned correctly and results in failure if used as mentioned.
We should document the correct endpoint in the apidoc , which is the source of information for all the admins\end-users
What are the testing steps for this pull request?
POST /katello/api/capsules/:id/reclaim_space
is mentioned.POST /katello/api/capsules/:id/content/reclaim_space