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.

Description of problem:
Newer RHEL can support HTTPS kickstart, but the default is the Templates capsule feature enables HTTP.

Version-Release number of selected component (if applicable):
6.1 Beta

How reproducible:
Always

Steps to Reproduce:
1. Configure a capsule with TFTP and Templates feature (capsule-installer --tftp=true --templates=true)
2. Notice capsule-installer does not expose --templates-url option

Actual results:
/etc/foreman-proxy/settings.d/templates.yml has an HTTP url by default

Expected results:
--templates-url is exposed in the capsule-installer, and configures /etc/foreman-proxy/settings.d/templates.yml with the given URL.


Additional info:
It's available in the puppet-foreman_proxy module, the capsule just doesn't expose the option.

*** This bug has been marked as a duplicate of bug 1197806 ***