Tulip seems to have a lot of hidden “feature flags” that enable/disable functionality on one’s instance. It would be very nice to have transparency over what there is, and whether it is enabled or not without always having to go through support.
Hi @sebme,
We appreciate the product suggestion and are actively working on initiatives to provide more transparency in the configuration of instances. We want to ensure that customers have full visibility into their config so that instances perform predictably.
I’ll make sure to keep this thread updated as these efforts progress. We’re also working to substantially pair down this list of flags and provide more control direct to users, for example:
3 Likes
@sebme This would be helpful, especially for partners (who work with multiple instances).
Hello Fabien, are you currently able to view the IQ certificates for each of your customer instances?
Hello @kevin.kononenko.
Unfortunately I know neither what you are referring to nor where to find it 
Would you mind rephrasing this?
So when we release a new LTS version of Tulip to our customers, we also give them an “IQ Certificate” which is meant to prove the integrity of the release. In other words, it has been set up in the way that it was intended. This must match across dev, test and prod instances. This is a PDF document. Have you seen one before?
@kevin.kononenko I think all the instances I manage use standard releases so I guess it’s normal that I didn’t receive any IQ certificate.
I must confess I fail to see the relationship with this question and this topic (visibility of feature flags)?
Understood. The IQ certificates contain a summary of the feature flag configuration, so that is our standard method of communicating this.
So, if we had an automated way for you to generate an IQ certificate at any time for each instance, would that solve the problem?
@kevin.kononenko Displaying flags in a webpage would be more user-friendly but if you want a solution that’s quick-and-easy to implement, that would work for me. I don’t check flag configuration often so I wouldn’t mind generating an IQ certificate.
By the way, what does IQ stands for?
You can learn more about the theory here: Installation Qualification (IQ) | Propel Glossary
Also, I am curious, how did this come up for you? Is there one particular feature flag that was varying across instances and creating different behavior, or is it just a general need for reporting?
@kevin.kononenko It’s closer to one (or several) flag(s) varying across my instances; I have no reporting needs for now. In my case, I had to enable some flags on some instances but not others. I asked for this at different moments time and sometimes for different reasons. Seeing this list of flags would allow me to:
- be reminded of which flags have been enabled or not so far on a given instance
- be reminded of which features are enabled by flags and which ones are always there
- figure out why something can be done on an instance and not on another
- know what optional features are available, some being potentially interesting for my customers
1 Like