Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[fingerprint] - Onboard to Azure ExP #1260

Closed
Tracked by #705
savannahostrowski opened this issue Dec 12, 2022 · 5 comments
Closed
Tracked by #705

[fingerprint] - Onboard to Azure ExP #1260

savannahostrowski opened this issue Dec 12, 2022 · 5 comments

Comments

@savannahostrowski
Copy link
Contributor

We will want to investigate how we can onboard to ExP so that we can A/B test features and conduct controlled rollouts.

@weikanglim
Copy link
Contributor

@savannahostrowski I think when we last spoke, you mentioned that this is something we need to do in azd. Is that covered with the work in #1715?

@savannahostrowski
Copy link
Contributor Author

No, I think we'll still want to onboard to the experimentation platform long term. I'm thinking that it'd be beneficial when we ship fingerprinting and potentially want to iterate on the implementation/heuristics etc.

@weikanglim weikanglim changed the title Onboarding to the experimentation platform [fingerprint] - Onboard to Azure ExP Aug 8, 2023
@ellismg ellismg assigned ellismg and unassigned weikanglim Aug 22, 2023
@rajeshkamal5050
Copy link

@ellismg anything pending here? can we close?

weikanglim added a commit that referenced this issue Sep 6, 2023
Allow experimentation rollouts to control the default alpha feature enablement.

- If a feature flag for `alpha_<featureId>` is set to true, the alpha feature is enabled by default. User config takes precedence over the default.

Also, moving the experimentation initialization to later in app initialization so that initialization only occurs when a command is fully parsed. Error commands should not trigger the flow.

Partially addresses #1260
@savannahostrowski
Copy link
Contributor Author

@weikanglim @ellismg did we configure the bits for the controlled rollout yet? Or just the client onboarding?

@weikanglim
Copy link
Contributor

weikanglim commented Sep 6, 2023

@savannahostrowski Controlled rollout is done with #2703. Closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants