Using Azure App Configuration for feature flags in short lived applications

Question

In our project we use approach with short lived branches which are merged into master branch. CI pipeline creates short lived application for almost every short lived branch. Every short lived application should have own state of feature flags.

Is it fine to create new App Configuration using REST API for every short lived application to store feature flags?

J. Campbell · Accepted Answer · 2020-12-06 17:16:54Z

1

"Fine" here may be subjective. A standard tier App Configuration instance has a daily charge of $1.20 (latest pricing info). If you are creating one of these, even if for a short time, the daily charge will still be incurred. A free tier store could be used, but there is no SLA on free tier stores.

I don't think incurring a charge per pipeline execution is desired. I would try to use the label property of App Configuration key-values to separate the settings required by different pipelines.

answered Dec 6, 2020 at 17:16

J. Campbell

7404 silver badges5 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Using Azure App Configuration for feature flags in short lived applications

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related