I really did not want to resort to this but I could not find any answers
from previously asked questions on the subject. The template is properly
creating the csrf_token hidden field which is being submitted to the server,
but I could not figure out why it was not using it it.
This fixes https://github.com/voxpupuli/puppetboard/issues/198
This will not be permanent, will have to look into upgrading the flask-wtf
and WTForms packages to the latest versions.
Fixes https://github.com/voxpupuli/puppetboard/issues/209
The event_count queries for the reports in the reports() and reports_node()
functions were always filtering on environments, even if all environments, *,
were selected. This update removes the environment clause from the query
string if 'All Environments' are selected
Using new Node and Catalog fields available in pypuppetdb 0.2.1
With the latest_report_hash field available on the Node object the report_latest can be partially deprecated. Will hopefully be removed in the next major/minor release.
Showing the Code ID field in the catalogs page. This is currently
unused in PuppetDB as of 3.2.2 but may be useful when it will be used
If available, using the latest_report_hash field of the node object
in the index and nodes templates for the link to the latest report
available for the node.
Updating the report_latest function in app.py to query the nodes
endpoint and redirecting using the latest_report_hash field if available.
If not query the reports endpoint for the node's latest report.
Fixed https://github.com/puppet-community/puppetboard/issues/193
Fixed Semantic UI tables set a fixed position on the applied tables
that do not affect the alignment with narrow browser windows. Downside
of this approach is that users will have to scroll horizontally to view
the entire catalog comparison.
In the previous commit the environment loading was moving to each request
and that functionality change was not reflected in the error processor
functions (for 4xx and 5xx series errors)
Moving the global environment list from a global context to a functional
context because octomike reported that the environment list in his environment
was not being refreshed.
Adding CHANGELOG entries for 0.1.1 and this new change.
Allow to list all nodes again (remove environment filter)
Adding a configurable default environment setting in case some environments to not have a 'production' environment.
Adding a '*' option to remove environment filters.
puppetboard: Adding PuppetDB 3.x support
Some of the implementations here is:
- Environment Awareness with a dropdown menu to switch environments
- First implementation of pagination in the form of a macro for flexibility
- Use of the PuppetDB 3.x APIs, therefore PuppetDB 2.x compatibility is broken
@daenney would rather have the footer reference the Puppet Community organization
than completing removing this bar.
Also adding a reference in README.rst about the available Google Group
Moving the envs variable out of the functions scope to the global scope,
this enables each function to reference and use these values.
Adding a new function check_env() to standardize the way to ensure that
the request environment exists, if it doesn't then abort with a 404.
This reduces 16 blocks of code and is in line with @daenney's suggestions
This bar reduces the available vertical space and other maintainers feel
it better to remove it than to modify it.
Also reducing the specific mention of @daenney from README.rst since he
has steped down as main project maintainer.
b4f74e240d
Making catalog tables searchable
7a8ddde6ca
Navbar style/naming simplifications
e8fea997fd
Creating Semantic UI Menu for environment switching instead of select menu
Make Puppetboard work with the PuppetDB V4 api
This PR just enables the basic functionality of PuppetBoard with the new PyPuppetDB version. https://github.com/puppet-community/puppetboard/pull/176 includes this work as well as other work to make better utilization of the new library
