Bunting for Craft CMS

Bunting is a Craft 6 plugin. Craft 6 is still in beta, and so is Bunting (6.0.0-beta.1) — try it on staging first and use caution on production sites.

FAQ

Does Bunting work on Craft 5? No. It’s a native Craft 6 plugin. Craft 6 is in beta, and so is Bunting — use caution on production.

Why are flags split between project config and the database? So a flag ships with the code that checks it, but can still be switched off on production in a hurry, where admin changes are usually disallowed.

I already use Pennant. Will Bunting take over? Bunting becomes the default store unless you turn that off, and features you define yourself keep working on it. If you’d rather keep your own default store, turn the setting off and use Feature::store('bunting') or bunting.active() for Bunting’s flags. Bunting never touches Pennant’s features table.

How do I launch on one site first? Set the flag to Off, and the site to On for everyone (or By rules). See Flags and rollouts.

Are percentage rollouts random each visit? No — each person has a fixed place per flag, so they see the same thing every time, and raising the percentage only adds people.

Do guests count in a percentage rollout? Only with Percentage rollouts for guests on, which uses a first-party cookie.

Can my front end ask whether a flag is on for another user over GraphQL? No. buntingFlags answers for the requesting user (or a guest) only, and only for public flags.

What happens when I delete a flag? Code that checks it sees it as off. Condition rules that use it stop matching. Its audit history stays.

More plugins

Pairs well with Bunting