v3.5.7

Bugfix, when a user deletes a feature on a group page, redirect back to that group page. Thanks @maxprokopiev!

v3.5.6

Update the docker image to run as an unprivileged user.

Update the target ruby version to 2.5.1.

v3.5.5

Update gem dependencies including a security patch on sinatra.

Add in a /metrics endpoint for prometheus to give basic http request metrics

v3.5.4

Added create/update timestamps to the features.

Fixed the date-pickers on the edit pages.

Some stylistic changes to the features table.

Thanks @samzilverberg for the updates. :)

v3.5.3

Dockerfile update to include additional packages:

• openssl
• ca-certificates

This solves some SSL issues on alpine based images.

v3.5.2

Addition of a new ENV variable LOG_LEVEL. By default Bandiera will log at INFO upwards, if this is not your preference, you can now change this using this variable. Accepted inputs are the constants in Logger::Severity i.e. DEBUG, INFO etc.

Added some DEBUG logging outputting the response from Bandiera to a v2 API request. This doesn't contain any user identifying data, but can be useful for users/admins when debugging flag/api issues.

v3.5.1

Addition of a new ENV variable STACKDRIVER_JSON_LOGGER - if this is present at runtime, the logs will be output in JSON that is suitable for being consumed by Google Cloud's Stackdriver logging.

Addition of a new ENV variable SENTRY_DSN - if this is present at runtime errors will be reported to the configured project on sentry.io.

v3.5.0

Addition of a new groups page on the bandiera UI. Thanks @samzilverberg!

v3.4.2

Update logging to remove user identifiable data in preparation for the GDPR laws to come into effect. Bandiera no longer logs ip addresses or user identities (if ran under basic auth), and will not log the user_group URL param by default. This can be re-enabled by setting the environment variable "SHOW_USER_GROUP_IN_LOGS" to "true" if it is desired.

v3.4.1

New feature - audit logs. Whenever a feature is created, changed or removed the activity is output to the logs; if an environment variable of RECORD_AUDIT_RECORDS is set to true, these log messages will be persisted in the database. Thanks @jshiell!

New feature - healthcheck endpoints. /healthz, /status/live and /status/ready can now be probed by external healthcheck applications.