Unleash 5.3: Playground additions, flexible webhooks, and transparent segments
Here comes Unleash 5.3! This month we’re focusing on flexibility, plus a quick update on telemetry data.
Playground 2.0: Run multiple variables across multiple environments at once
A new version of our playground is live, and boy is it robust.
You can now select multiple variables across multiple environments, then run them all at the same time.
You can also run multiple sets of context variables such as userIDs simultaneously.
An obvious use case for this is for debugging or testing. You’ll probably find a ton of other ways to take advantage of Unleash’s advanced playground.
Read more about our playground in our spectacular documentation.
Customize HTTP headers for webhooks
You can now pass any HTTP header that you want as part of our webhook add-on.
This means your webhooks are no longer limited by things that pass content-type and authorization. Really, you should be able to pass pretty much anything else you want through the Extra HTTP Headers field.
More on webhooks in our documentation. It’s pretty thorough.
Keep track of where you use your segments
This update is mostly quality of life: You can now see where a segment is being used.
This includes projects, flags, and context fields.
Read all about segments in our user-centric documentation.
Telemetry data update
Finally, a quick update to how we collect data. Don’t worry, privacy is still incredibly important to us, and we will not collect PII or user data.
We are curious as to how Unleash is being used across all our users. We’ve begun to look at the general data of things like the number of active feature flags in use, or the total number of projects in a system.
Your current data telemetry settings will remain unchanged. If you’ve already opted out, you’re still opted out.
Read more about the data Unleash collects–as well as how to manage your data collection settings–in our open documentation.