PowerShell-FeatureFlags
PowerShell-FeatureFlags copied to clipboard
microsoft
PowerShell module containing a Feature Flags implementation based on a local config file.
We should have a daily test where we install the cmdlets from PSGallery and run a simple test to verify that the most common user journey (download from PSGallery) works...
```[tasklist] ### Developer docs - [ ] Document target runtimes and dev environment - [ ] Explain how to run the scripts to get all dependencies and run tests. -...
Deterministic, cheap evaluation of all feature flags; ability to use feature flags in batch scripts in a cheap way.
See discussion in https://github.com/microsoft/PowerShell-FeatureFlags/pull/35. It doesn't seem trivial to update the code to support NJsonSchema 10.x, but at some point we should do it (or use another library like https://github.com/gregsdennis/json-everything).
The PowerShell code works, but at this point it might be better to implement the cmdlet in pure C#. This should buy us some more advantages, as the `dotnet` tool...
There are some classes of errors which are not syntactic or semantic errors, but might indicate misconfiguration, and that could be considered warnings. For example, the presence of stages that...
Azure Artifacts can be used as a PowerShell repository (it's NuGet after all): https://docs.microsoft.com/en-us/azure/devops/artifacts/tutorials/private-powershell-library?view=azure-devops It would be nice to automatically test: - upload to PSGallery; - fetch from PSGallery; -...
Consider: - environment variables; - probabilistic evaluation; - dumping evaluated feature flags.