Commit Graph

8 Commits

Author SHA1 Message Date
Clark Boylan 3caf0cf70d Retire this project
We've shutdown the kibana service and don't need to manage it with
puppet any more.

Depends-On: https://review.opendev.org/c/openstack/project-config/+/839235
Change-Id: Iad395dfc91b9c7523b735b31da4dec2721acc42c
2022-04-25 09:43:47 -07:00
Clark Boylan 073ef439a7 Use full lookup path for serveradmin in template
The last change was incomplete bceause we evaluate the apache conf
template in the context of the httpd class meaning any vars outside of
that class must be fully qualified lookups. Make serveradmin a fully
qualified lookup.

Change-Id: I709af6a78316cd1ca7e489d62f13e988997f3157
2018-12-14 15:40:03 -08:00
Colleen Murphy 74e6af7fd7 Fix template variables
When serveraliases is not defined it should evaluate to nil, not ''.
Check for both to cover our bases.

Change-Id: Ie69baf01963f33cf695a0de763af75dc33b67daa
2018-07-12 14:34:59 +02:00
Zuul 4902600dd1 Merge "Fix scope of vhost template variables" 2018-06-12 22:33:33 +00:00
Colleen Murphy de1b7966d4 Fix scope of vhost template variables
Dynamic scoping for variables in ERB templates was removed in puppet
4[1] which means that the variables defined in the
kibana::js class cannot be found when it is referenced in
the httpd::vhost defined type and will be evaluated as nil when
puppet runs. Use scope.lookupvar instead to be explicit about the
variable's source.

[1] https://puppet.com/docs/puppet/4.10/lang_updating_manifests.html#dynamic-scoping-in-erb

Change-Id: I27a63e74bda27269145b58e6d237c440085f0709
2018-04-27 19:50:28 +02:00
Colleen Murphy efba033351 Use instance variables in puppet template
Using local ruby variables in puppet ERB templates was deprecated in
puppet 3 and doesn't work any more in puppet 4. Access these values as
ruby instance variables instead.

Change-Id: I06bdd6f5b1f13c4970c5e3e9dc8be4cf8d919b03
2018-04-26 23:05:46 +02:00
Clark Boylan 0a62118c0e Support Apache 2.4 ACLs
We need to use Require all granted in our directory that hosts the
Kibana files otherwise we get 403 forbidden when trying to access the
content.

Change-Id: I2e14ba113705f3fabaa4920704589da0f9abe978
2016-05-26 15:15:42 -07:00
K Jonathan Harker 8c66da99df Add kibana3 support
Add support for the javascript version of kibana.

By default, this is done by serving both the kibana and also an
elasticsearch proxy from the same location. Allowed GETs and POSTs
for read-only access to elasticsearch are passed to a proxy and all
other requests are served from the kibana source directory.

An optional prefix, such as 'elasticsearch/', can be specified in which
case the reverse proxy to elasticsearch will be served from this
sub-path.

Change-Id: I13f9dff0bbd6498a36dc75b026c9042a9bb05e8f
2015-10-14 12:18:31 -07:00