keystone::endpoint admin_protocol parameter

[Derek Yarnell]

In the examples directory for apache ssl support for keystone there is a example with

class { 'keystone::endpoint':
        public_address => $::fqdn,
        admin_address => $::fqdn,
        internal_address => $::fqdn,
        public_protocol => 'https',
        admin_protocol => 'https'
 }

This is rejected as the keystone::endpoint class does not have the parameter admin_protocol available. Is this on purpose and the example is just wrong or was this an oversight? Or is it not possible to secure the admin/internal keystone interfaces? It seems that the protocol for admin and private are hard coded to http (in manifests/endpoint.pp)

keystone_endpoint { "${region}/keystone":
    ensure => present,
    public_url => "${public_protocol}://${public_address}:${public_port}/${version}",
    admin_url => "http://${admin_address}:${admin_port}/${version}",
    internal_url => "http://${internal_address}:${real_internal_port}/${version}",
    region => $region,
 }

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/173566

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/173566
Committed: https://git.openstack.org/cgit/stackforge/puppet-keystone/commit/?id=3f0c6d5f96d84108d03f0fec0a477cb714baca64
Submitter: Jenkins
Branch: master

commit 3f0c6d5f96d84108d03f0fec0a477cb714baca64
Author: Emilien Macchi <email address hidden>
Date: Tue Apr 14 18:11:07 2015 -0400

    examples: fix apache_with_paths.pp

    Minor fix for examples, to avoid any confusion.

    Change-Id: I6e07b0823b141f65be237303a15520d46cda5e5a
    Closes-bug: #1267627