Joanthan

hi @askulkarni2 I tried using `terraform destroy -target="module.eks_blueprints_kubernetes_addons" -auto-approve` first and it still failed with the same error for me.

I don't think its the provider thats the issue for me. When I hard code my eks cluster name like below instead of using `module.eks_blueprints.eks_cluster_id` the destroy works okay. ```terraform...

> I was sure I had the same issue on destroy this am and through testing, copied the kubectl provider block from an eariler working setup and it fixed the...

Unfortunately I ran into the same issue with using `provider "kubectl"`.

One way I've gotten this to work is for Step 2 in the original post, do the following: ```bash $ export PR_NUM="ignore" $ bump2version minor --serialize ""major}.{minor}.{patch}" # results in:...

```python def main(): numbers = list(range(5)) for number in numbers: one_hundred_list = list(range(100)) squared = next(filter(lambda x: x == number**2, one_hundred_list)) print(squared) # This will print 0, 1, 4, 9,...

Hey guys, I would like this feature too. I would like my terragrunt commands to fail if the s3 bucket isn't created yet. @brikis98 I tried doing `terragrunt init --terragrunt-no-auto-init`...

@tanvp112 yes I see the name that I am expecting. @dhf22 I had a workaround where I had to hard code the name of the cluster instead.

I'm running into the same issue as you guys and my work around was to put a description in the function properties with a unique string every deployment. Is `AutoPublishCodeSha256`...

@rmk135 ah i see the difference is between generators and context managers. From my understanding the `Resource` provider is used to initialize the resource with the `init_resources()` method and clean...