Red Hat Bugzilla – Bug 1273059
content_type parameter as not required in Table 68.2 of Create a Custom Repository section
Last modified: 2016-10-05 21:28:41 EDT
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:
tested against: sat6-Satellite-6.1.0-RHEL-7-20151016
Mass re-assign of all content / lifecycle related bugs to Dan MacPherson for the new content management guide.
++++ 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. /////////////////////////////
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.
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.