https://github.com/ALM-Rangers/azurefunction-vsts-feature-flags
Sample code to demonstrate the use of feature flags in extensions using LaunchDarkly service
https://github.com/ALM-Rangers/azurefunction-vsts-feature-flags
Last synced: 6 months ago
JSON representation
Sample code to demonstrate the use of feature flags in extensions using LaunchDarkly service
- Host: GitHub
- URL: https://github.com/ALM-Rangers/azurefunction-vsts-feature-flags
- Owner: ALM-Rangers
- License: other
- Archived: true
- Created: 2017-09-06T14:55:19.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2018-05-07T16:15:05.000Z (almost 7 years ago)
- Last Synced: 2024-08-03T22:06:25.392Z (9 months ago)
- Language: C#
- Size: 121 KB
- Stars: 12
- Watchers: 26
- Forks: 2
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Contributing: .github/CONTRIBUTING.md
- License: LICENSE
Awesome Lists containing this project
- awesome-launchdarkly - ALM-Rangers/azurefunction-vsts-feature-flags - building extenstions with feature flags (Apps)
README
# azurefunction-vsts-feature-flags
This sample solution shares the outcome and learnings from our feature flags and A|B testing research.
For more details, refer to these blog posts:
- [How to implement feature flags and A|B testing](https://blogs.msdn.microsoft.com/visualstudioalmrangers/2017/04/04/how-to-implement-feature-flags-and-ab-testing/)
- [Building VSTS Extensions with feature flags](https://blogs.msdn.microsoft.com/visualstudioalmrangers/2017/06/27/building-vsts-extensions-with-feature-flags/)
- [Building VSTS Extensions with feature flags – Part 2](https://blogs.msdn.microsoft.com/visualstudioalmrangers/2017/07/18/building-vsts-extensions-with-feature-flags-part-2/)
- [Building VSTS Extensions with feature flags – Part 3](https://blogs.msdn.microsoft.com/visualstudioalmrangers/2017/08/10/building-vsts-extensions-with-feature-flags-part-3/)
- [Azure Functions – Prepare for continuous delivery](https://blogs.msdn.microsoft.com/visualstudioalmrangers/2017/09/06/azure-functions-prepare-for-continuous-delivery/)
- [Azure Functions – Azure Function – Integration tests automation](https://blogs.msdn.microsoft.com/visualstudioalmrangers/2017/09/24/azure-function-integration-tests-automation/)
- [Azure Functions – CI / CD DevOps Pipeline](https://blogs.msdn.microsoft.com/visualstudioalmrangers/2017/10/04/azure-function-ci-cd-devops-pipeline/)
- [Azure Functions – Integrating monitoring with Application Insights](https://blogs.msdn.microsoft.com/visualstudioalmrangers/2017/10/10/azure-function-integrating-monitoring-with-application-insights/)
> We're using this sample to implement feature flags in our extensions. We're dogfooding and validating our research!
## Contributors
We thank the following contributor(s) for driving the research and this sample: [Mikael Krief](https://blogs.msdn.microsoft.com/visualstudioalmrangers/2015/05/26/introducing-the-visual-studio-alm-rangers-mikael-krief/), [Shmulik Ahituv](https://blogs.msdn.microsoft.com/visualstudioalmrangers/2016/09/28/introducing-the-visual-studio-alm-rangers-shmulik-ahituv/)
## Contribute
Contributions are welcome. Here is how you can contribute:
- Submit bugs and help us verify fixes
- Submit pull requests for bug fixes and features and discuss existing proposals
Please refer to [Contribution guidelines](.github/CONTRIBUTING.md) and the [Code of Conduct](.github/COC.md) for more details.
## Data/Telemetry
This project collects usage data and sends it to Microsoft to help Microsoft improve its products and services. For more information about how Microsoft uses telemetry data, read the Microsoft [privacy statement](http://go.microsoft.com/fwlink/?LinkId=521839).
This telemetry is used for A|B testing and troubleshooting.
To turn off telemetry you need to fork this repo, publish, and use your own version of the project after removing the ApplicationInsights configuration key.