CloudBees Feature Management - Python changelog

Variant('default_string', ['string_1', 'string_2']) ⇒ RoxString('default_string', ['string_1', 'string_2'])

Some trivial parameters (mostly type) validations were added to dynamic_api and flags constructions. For example: RoxString(None) will raise an TypeError as default cannot be None (default value of RoxString should be a string and defaults to an empty string if no default is provided). Rox.dynamic_api.value(None, 'default_string', ['string_2', 'string_3']) will raise an TypeError because of None flag name (name should always be a string)

register(container) will register the container under an empty string namespace (multiple register calls with the same namespaces are still not allowed!)

It is recommended to wrap all handlers used in Rox platform (all Rox.set_custom_<…​>_property, RoxOptions.impression_handler, RoxOptions.configuration_fetched_handler, RoxOptions.dynamic_properties_rule) with try-except in order to be in the right context. In case there will be an uncaught error, it will reach the Rox.set_userspace_unhandled_error_handler handler. You can use this handler for debugging, or for further error handling. An Error thrown within this handler will be written to log. If no set_userspace_unhandled_error_handler was set, errors will be written to the log.

Starting with SDK 5, flags will always send impressions after setup (not only when targeting is enabled on the dashboard)

As experiments were removed, impressions handler signature was changed from (reporting_value, experiment, context) to (reporting_value, context). reporting_value now also has a Targeting (boolean) property, indicating the flag was evaluated by using the dashboard configurations.

In addition to RoxFlag and RoxString, we also added RoxInt and RoxDouble

DynamicApi was also updated with matching get_int and get_double methods

In order to clean all background Tasks

multiple Rox.setup calls will be ignored if Rox wasn’t Shutdown in between