Henry Barrow

That's great to hear!

Hey @rickardp, Thanks for bringing this to our attention. I've created an internal ticket to investigate what is happening here. We'll be sure to update this issue as we learn...

Hey @Gilles95 and @rickardp, By default, the `launchdarkly_project` resource is used to manage a single project and *all* of it's underlying environments. If you wish to only manage a subset...

That's good info @rickardp. If you have more than 20 envs then it does seem likely that #154 is related.

> I upgraded our provider to version 2.13.2, Terraform to 1.5.3 and we see the same result, when removing an environment block in the middle of the list, it renames...

> Could this be related to #154? Maybe pagination is why updating the environments get the provider confused. There were more than 20 environments in the original case when I...

> > Hey @Gilles95, I did some investigation and you are seeing this plan change because the `environments` block is implemented as a [`TypeList`](https://developer.hashicorp.com/terraform/plugin/sdkv2/schemas/schema-types#typelist) under the hood. We chose to...

> > > Could this be related to #154? Maybe pagination is why updating the environments get the provider confused. There were more than 20 environments in the original case...

Hey @joe-hutchinson-cko, can you share what your config looks like (specifically the `team_key`)? I ask because it sounds like you may need to take advantage of the [`depends_on` meta-argument](https://developer.hashicorp.com/terraform/language/meta-arguments/depends_on). Depending...

Thanks for sharing. Given that you are using the output from the `okta_group` resource it sounds like the issue is a propagation delay between when the Okta group gets created...