Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.