Arthur Halet

thanks for your thoughts @ScottGuymer . `id_bg` could be used here yes @dwaynebailey but it is applied when the previous app which already have policies has been deleted before the...

That was actually already documented: https://registry.terraform.io/providers/cloudfoundry-community/cloudfoundry/latest/docs/resources/app#update-resource-using-blue-green-app-id I let it open as a reminder to have a true zero-downtime for network policy. Thanks for your feedbacks @ScottGuymer

we have client for v3 api already in our code and useable, but combine both is for now quite complicated to handle. For now just some features are selected and...

I'm more in big bang change for switching on v3 by switching all resources on v3 like the cli is actually doing it (with 2 different versions of the cli...

what's your version of terraform ? can we see your tf files please ? You can also use `depends_on` parameter: https://www.terraform.io/docs/configuration/resources.html#depends_on-explicit-resource-dependencies but here it should not do things in this...

Could you provide your tf file and give us the terraform that you are using ? do you use `id_bg` (see https://github.com/cloudfoundry-community/terraform-provider-cf/wiki/resource_app#attributes-reference ) ? Do you have the same issue...

We can do as the cli does, do the update on the app to add more buildpacks like official cli still not use v2. We have already prepared all v3...

I think you're talking about this github action: https://github.com/GSA/datagov-ssb/runs/2224255533?check_suite_focus=true It doesn't look like that it contains changes in this terraform plan (we don't even see the switch between true and...

For the state you could also simply change `fail_when_catalog_not_accessible` to set false inside it. I understand your frustration so I went deeper, it looks like I can't access to changes...

please see the pull request and give it a try