Bug 1273059

Summary: content_type parameter as not required in Table 68.2 of Create a Custom Repository section
Product: Red Hat Satellite Reporter: Roman Plevka <rplevka>
Component: Docs API GuideAssignee: satellite-doc-list
Status: CLOSED WONTFIX QA Contact: satellite-doc-list
Severity: medium Docs Contact:
Priority: medium    
Version: UnspecifiedCC: adahms, dlackey
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-06 01:28:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Roman Plevka 2015-10-19 13:40:48 UTC
Document URL: 

Section Number and Name: 
68.2 [Create a Custom Repository]
Describe the issue: 
The table no. 68.2 states a "content_type" parameter as not required
but the parameter is required (no default value)

$ curl -k -X 'POST' -u admin:changeme -H "Accept: application/json" -H "Content-Type: application/json" -d '{"name": "my_yum_repo_1", "product_id": 1, "url":""}' https://<FQDN>/katello/api/v2/repositories

{"displayMessage":"Validation failed: Content type must be one of the following: yum, file, puppet, docker","errors":{"content_type":["must be one of the following: yum, file, puppet, docker"]}}

Suggestions for improvement: 
change required - False to True
Additional information:

Comment 1 Roman Plevka 2015-10-19 13:42:04 UTC
tested against:
sat6-Satellite-6.1.0-RHEL-7-20151016

Comment 3 Deon Ballard 2015-12-02 19:36:07 UTC
Mass re-assign of all content / lifecycle related bugs to Dan MacPherson for the new content management guide.

Comment 4 Deon Ballard 2015-12-10 17:21:27 UTC
++++ IMPORTANT +++++

These bugs are being reassigned to Dan MacPherson as part of his work on creating a content management guide.


/////////////////////////////
DO NOT REASSIGN TO THE QUEUE.
/////////////////////////////

Comment 5 Dan Macpherson 2016-02-03 05:54:02 UTC
This is an API bug, but applies to the 6.0 API guide. From what I understand, the 6.1+ API Guide has changed and links to in-application API reference. This BZ might not be needed any more.

Comment 6 Andrew Dahms 2016-10-06 01:28:41 UTC
This section no longer exists in the current version of this guide, and efforts are underway to provide a more detailed reference to the available methods.

Closing this bug for now.