From c0bd689636e14ed64c702e9178d82df82f556550 Mon Sep 17 00:00:00 2001 From: Yanis Guenane Date: Tue, 8 Sep 2015 13:01:48 +0200 Subject: Allow one to specify horizon ALLOWED_HOSTS If horizon is running in production (DEBUG is False), it will answer only to the IPs/hostnames specified in the ALLOWED_HOSTS variable in the local_settings.py configuration file. The puppet-horizon module offer the feature to customize that, tripleo-heat-teamplates was missing the link between the top-level parameter and the puppet parameter, hence this commit. More info : * https://docs.djangoproject.com/en/dev/ref/settings/#allowed-hosts * https://github.com/openstack/puppet-horizon/blob/master/templates/local_settings.py.erb#L14-L24 Change-Id: I5faede8b74a0318e15baa761dc502b95b051ae0d --- puppet/hieradata/controller.yaml | 1 - 1 file changed, 1 deletion(-) (limited to 'puppet/hieradata') diff --git a/puppet/hieradata/controller.yaml b/puppet/hieradata/controller.yaml index a4e2766b..90c2705f 100644 --- a/puppet/hieradata/controller.yaml +++ b/puppet/hieradata/controller.yaml @@ -90,7 +90,6 @@ pacemaker::resource_defaults::defaults: resource-stickiness: { value: INFINITY } # horizon -horizon::allowed_hosts: '*' horizon::django_session_engine: 'django.contrib.sessions.backends.cache' # mysql -- cgit 1.2.3-korg