When rebuilding flights for a tenant, all flags need to be considered (especially the ones which are in Azure App Config)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 15/100
Research direction
The issue provides no files, tests, or entry point, so first map the tenant flight rebuild flow and its Azure App Configuration integration. Confirm which flags are currently included and define done as rebuilding a tenant while considering every flag, including those stored in Azure App Configuration.
Written by the indexing model from the issue text.
Description
This issue has no description.
- Dominant language
- C#
- Stars
- 50
- Forks
- 19
- Avg merge
- 8d 16h
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/FeatureFlightingManagement
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
documentation
microsoft/FeatureFlightingManagement#33 · 1 assignee ·
-
performance issue
microsoft/FeatureFlightingManagement#26 · 1 assignee ·
-
Performance issues Openhelp wanted performance issue
Difficulty 4/5 3-5 days Newbie friendliness 20/100
All issues in microsoft/FeatureFlightingManagement
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·