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

Modifying the defaults affects the client-side availability #199

Closed
hamamou opened this issue Feb 21, 2024 · 1 comment
Closed

Modifying the defaults affects the client-side availability #199

hamamou opened this issue Feb 21, 2024 · 1 comment

Comments

@hamamou
Copy link

hamamou commented Feb 21, 2024

Hi,
Let's assume, I deployed a feature flag using this configuration

resource "launchdarkly_feature_flag" "your-feature-flag-key" {
    project_key    = local.project_key
    key            = "your-feature-flag-key"
    name           = "Your feature flag name"
    description    = "Your feature flag short description"
    variation_type = "boolean"
    tags           = ["some", "tags"]
    temporary      = true

    variations {
        value = false
    }

    variations {
        value = true
    }

    defaults {
        off_variation = 0
        on_variation  = 1
    }

    client_side_availability {
        using_environment_id = true
    }
}

If I modify the defaults of one of the variation off_variation = 1, the client-side availability is also updated, which I don't think is expected.
image

Thank you.

@hamamou
Copy link
Author

hamamou commented Feb 22, 2024

This was fixed in 2.10.0.
Thanks

@hamamou hamamou closed this as completed Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant