This message was deleted.

I think this looks pretty good so far! any specific questions you might have?

Hey lee thanks for looking into this. I’ll split questions to make it easier to reply

Are there any resources about using feature flags with pulumi that I might have missed?

not that I’m aware!

Are the stack config files the best place to toggle feature flags?

yes i think this is a valid strategy! You can also read feature flags using SDKs (because you can use standard code, which is a nice benefit!) from feature flag providers like launchdarkly, but your strategy is straightforward and well implemented

feature flags need to be managed carefully and can clutter code. Do you use feature flags in your pulumi projects or not worth the bother?

We use a third party feature flag provider for the Pulumi service

If the stack config files is the best place to toggle feature flags, am I calling them in the best way?

I think at the moment you’re using the feature flags as inputs. You could also just have boolean flags:

if (config.feature_enabled) {
  // do something 
}

but what you have now looks great!

I’m thinking of writing GitHub action to flag obsolete feature flags which are enabled in prod. Should I parse the yaml config files or can I somehow use the pulumi outputs?

You could use automation API for this! Our pulumi github action uses this, and you can read and set config values programmtically

Thanks Lee this is really helpful (and reassuring 🙂 ) I’ll have a look about using the Automation API to flag (and perhaps set) the feature flags. Have a good evening!

Not at all, thanks so much ❤️