v1.5.9 🌈

Changes

🚀 Features

• Add external feature link and make it clickable in the UI @IrinaSouth (#844)
• Add ability to add metadata as simple string @IrinaSouth (#838)
• Add ability to add metadata on a feature to the UI and format it as JSON @IrinaSouth (#834)
• Add ability to rename service accounts + UI improvements @IrinaSouth (#824)

🐛 Bug Fixes

• Various UI responsiveness fixes @IrinaSouth (#858)
• Admin UI - make selectable text @IrinaSouth (#846)
• SAML - Single login bugfix @rvowles (#829)
• UI - fix loading indicators @IrinaSouth (#811)
• Fix error messages and add a util method for url validation @IrinaSouth (#810)

📝 Documentation

• Fix "search" function in main docs @IrinaSouth (#861)
• Restructure and improve docs and UI improvements @IrinaSouth (#831)
• FeatureHub documentation improvements @IrinaSouth (#820)

🧰 Platform Improvements

• Support Google Pub/Sub for platform as well as NATS @rvowles (#842)
• Add AWS Kinesis support @rvowles (#849)
• Support Fastly Cache on GET requests @rvowles (#818)
• Updated metrics @rvowles (#807)

v1.5.8 🌈

Changes

🚀 Features

• Formally support MariaDB @rvowles (#797)
• Admin SDK key refresh @IrinaSouth (#793)
• Add Admin SDK Key option to the UI @IrinaSouth (#788)
• SAML Support for FeatureHub @rvowles (#785)
• Admin Service Accounts @rvowles (#769)
• oauth2 token headers and form @rvowles (#776)
• Support Cache Control for website and APIs @rvowles (#751)

🐛 Bug Fixes

• Some dbs miss newly associated SA/Environments @rvowles (#798)
• Fix environments ordering functionality on Admin UI @IrinaSouth (#752)

📝 Documentation

• Add docs - admin service accounts @IrinaSouth (#796)
• Add SAML docs

📌 Dependencies

• Security dependency updates @rvowles (#782)

v1.5.7 🌈

Changes

🚀 Features

• Support Heartbeats in SSE @rvowles (#738)
• Support multi-architecture builds @rvowles (#736)
• Add feature description field to admin UI and metadata to the API @rvowles (#724)
• Add Change value/ retire permission to display in the Admin UI @IrinaSouth (#721)
• This allows individual environments to retire features at the end of their lifecycle @rvowles (#708)
• Admin UI - add user name on avatar hover in the App bar @IrinaSouth (#710)

🐛 Bug Fixes

• Fix: Environment ordering issues @rvowles (#716)
• Deleted users were allowed in by oauth @rvowles (#706)
• When OAuth2 login fails, the server should route to a nice page on the front end explaining what happened @rvowles (#701)
• Allow set cache control on Edge GET API @rvowles (#696)

📝 Documentation

• Support multiple docs versions per FeatureHub version
• Update "Retire feature" docs @IrinaSouth (#728)

📌 Dependencies

• Bump follow-redirects from 1.14.7 to 1.14.8 in /adks/e2e-sdk @dependabot (#715)

🧰 Platform Improvements

• Update how the Edge cache works @rvowles (#713)

Release 1.5.6

What's Changed

• [Fix] When updating service account permissions from Admin UI - changes don't get reflected when serving features #687. Fixed in PR #686

Note: If you are running multiple instances of Dacha (i.e. > 1 Dacha instances in "all-separate" installation option) then please make sure you dial them all back to 0 instances to force them to refresh their cache.

Release 1.5.5

Note: Please use 1.5.6 as a regression was introduced in 1.5.5 that was fixed in 1.5.6

What's Changed

• [Feature-AdminUI] Allow for a configurable base path for FeatureHub by @rvowles in #642
• [Feature-AdminUI] Expose "user last logged in" in Admin UI by @rvowles in #666
• [Feature-Backend] Introduce Version API by @rvowles in #646
• [Feature-Backend] Add in extra options for logging information (user, environment, web-headers) by @rvowles in #664
• [Feature-Backend] Enable auditing tracking by @rvowles in #668
• [Fix] Fix deleted environments not getting published by @rvowles in #656
• [Fix] H2 library version bump (security) by @rvowles in #665
• [Fix] Tokens for deleted users were not cleaned up by @rvowles in #669
• [Fix] Dacha losing feature changes as multiple copies are cycled through by @rvowles in #672
• [Fix] Fix test API creating duplicate feature values by @rvowles in #679

Full Changelog: https://github.com/featurehub-io/featurehub/milestone/19?closed=1

Release 1.5.4

What's Changed

• Change to log4j2 CVE 2.17 by @rvowles in #615
• canvas kit local download fix by @IrinaSouth in #618
• Add base support for Oracle DB by @rvowles in #624
• Add links to docs in the Admin app by @IrinaSouth in #622
• H2 Upgrade for Critical Severity by @rvowles in #629
• Non-breaking Changes to Edge/Dacha/MR by @rvowles in #635
• Fix json-editor in Admin app by @IrinaSouth in #637
• Fix serving rollout strategies in party-server-ish and edge-rest. Fix accessing flags/values when set first time by @rvowles in #638

Full Changelog: https://github.com/featurehub-io/featurehub/milestone/18?closed=1

Release 1.5.3

• Another Log4j2 security vulnerability fix (identified as per https://logging.apache.org/log4j/2.x/ and fixed in version 2.16.0)
• Fix health check issue

Release 1.5.2

Log4J library security vulnerability fix

Release 1.5.1

• Ability to reset API Keys from the Admin UI app
• Bug-fixes in the Admin UI app

For all tickets in this release please check here

Release 1.5.0

This release includes architectural changes to improve FeatureHub deployability onto the cloud platforms and improve overall performance. For the full list of GitHub issues see here

For the overview of recent improvements, please see below:

Admin Console Web App

support for Keycloak - this adds support for Keycloak - OAuth2 identity provider. Docs

Backend

Breaking changes

The breaking change only affects all-separate setups and only Edge configuration. Make sure you update
dacha.url configuration according to this docs

Non-breaking changes

super-light weight deployment option - A new bundled deployment, party-server-ish - which contains the Admin web app, the Admin backend (MR), and edge-rest together as one bundle. It is an ideal deployment for a low-use website and is covered in our installation docs. As it includes edge-rest it can’t be used for streaming updates, but if you have a mobile app or web app or you are OK with GET/polling updates, this is a low-cost deployment option.

light-weight edge services - edge splits into Streaming+REST and REST - so there are now two docker images, the existing one, edge which talks to dacha, and edge-rest which talks directly to the database. This makes edge-rest suitable for deploying into a container runtime platform like KNative, Google Cloud Run or Azure Container Instances.

reduced data egress costs - Edge now supports etag and this is now folding into the following SDKs: Javascript Node and Javascript Client. This significantly decreases data egress costs when features have not changed, and increases the ability to use a CDN in front of Edge if you wish.

deployment configuration - all configuration properties are now available in the same case as environment variables, previously they were required to be upper case and have . replaced with _. We did this for environments like Cloud Run and ECS.

enhanced, more performant, rest based cache - Dacha, our caching layer moves to being a REST server from being a NATS server with a monitoring only REST api. It is intended to be an internal only facing REST service but while it consumes the NATS updates from MR, it exposes its caching for REST purposes and enhances the data it returns (to include portfolio, application, etc).

database read replicas - All systems that talk to databases now support a read replica using the db-replica. or DB-REPLICA_ prefix for specifying configuration. This means an increased number of database connections, and balancing your read only queries into the read replicas. Docs installation docs

massive performance increases for GET requests - Significantly enhanced read operations for GET requests on Edge - we have really focused on performance here and managed to get a 9x performance improvement for the dacha based platform. The edge-rest based platform depends on availability of your database connections so will be a bit slower.