Roberto López López

Hi @blaksec , Thank you for this PR. Two remarks: * I can see that you have created [another PR](https://github.com/akamai/AkamaiOPEN-edgegrid-python/pull/58/files), I guess it is about the same issue. Please: close...

@inaitana : we will check what's the best approach here, no worries :-)

Please, merge this and [your other PR](https://github.com/akamai/AkamaiOPEN-edgegrid-python/pull/59/files)

Hi @danieldbr , As you can read in the [EdgeKV resource documentation](https://registry.terraform.io/providers/akamai/akamai/latest/docs/resources/edgekv), at this stage we just support inserting initial data. If the users need to update the edgekv namespace...

Hi @hypnotisttom , Thank you for your report, this quite probably is our fault :-) could you please add your `.tf` configuration for easier debugging from our side? Thank you....

Oh, thank you. Although it might not be a valid JSON, I think we should handle this properly (either validating the user input, or handling that panic before it happens)....

Hi @hypnotisttom , Regarding akamai_edgeworker: yes, deletion of a resource will trigger its deactivation in staging and/or production. Regarding akamai_cloudlets_policy: yes, you are once again right. As you can see...

@hypnotisttom : please, let me check with the respective teams. We have developed this a while ago and I might be wrong.

@hypnotisttom : Out of memory: upon cloudlet policy deletion, the activations are deleted on server side. Anyway SFTP propagation may be slow, which triggers [the mentioned error](https://github.com/akamai/terraform-provider-akamai/blob/master/pkg/providers/cloudlets/resource_akamai_cloudlets_policy.go#L401). When we apply...

Hi @hypnotisttom , I got an answer from the EW team: """ The implementation we have now is to reject the call to delete if there is an in-progress activation...