Using the puppet 4 future parser it is far more particular about
variables and their scoping. We don't set a serveradmin in this class
but then attempt to use it in the vhost template. This was fine under
puppet 3 as it would just look for this out of the current scope but
breaks under puppet 4.
Make this trivially happy on puppet 4 by setting a default that is sane.
Change-Id: Id415056cdfa693fd199e0b4a0c6b09e20faf23ef
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
The kibana apache vhost file makes use of mod rewrite and mod proxy but
we don't enable those modules explicitly here. We happen to enable them
in other places that use this puppet module but that leads to races and
isn't explicit enough. Go ahead and explicitly enable the deps in this
puppet module so that it is self sufficient.
Change-Id: Ic05f26d61f2ac4b5adffee98782d1a02931d5731
Order and intendation of those parameters are changed
to follow Puppet Style Guide recommendation [0].
Moreover, it will allow to an user to find much faster
a variable in a list of variables.
[0]. https://docs.puppetlabs.com/guides/style_guide.html
Change-Id: I7bd6abf2bc6b10da52fb4dad0c238b7b59cec54b
In order to make Share work without relying on elasticsearch write perms
we patch dashLoader.js to construct the urls based on the logstash
dashboard since it is deterministic anyways. This is a massive hack but
maybe it will be less terrible once ES is upgraded and we can use
kibana4.
Change-Id: I64cc693e5e188c68e134b4769ccc519f6191f36c
We update the default logstash dashboard to remove excessively short
refresh period options, default the query result listing output to
be timestamp and message, default to a 15 minute query instead
of a 24 hour query, and default to a blank query instead of '*" because
the '*' forces you to delete it to add any new queries but they are
functionally equivalent.
Change-Id: Id68a1f1e496f5d729b21aa2be30a5e2b73ab65fd
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
Clark Boylan