dd84ai

Results 11 comments of dd84ai

![Screenshot_20230820_181418](https://github.com/wagoodman/dive/assets/20555918/0032cdef-b249-4e9e-8de1-962c52b57e69) Layer Details is missing layer size. Which makes not accessible info beyond navigating list. Will be nice adding layer size into Layer Details :smile:

if you are using Ingress Nginx, there is elegant workaround for having basic auth at least by using its annotations which we can input in helm chart. Better than nothing...

> I see this has been added already via .Values.distributor.config.max_attribute_bytes. Do you still see value in this PR? @QuentinBisson , I see since 2.8.0 grafana https://github.com/grafana/tempo/releases/tag/v2.8.0-rc.0 the attribute was renamed...

@QuentinBisson also bless you for giving a check and sorting out, even if the result ended in closing of it. Nice to see some movement to be present now. Thank...

@dominikschulz recreating from zero on emtpy user - `adduser testuser` - `sudo usermod -a -G sudo testuser` - `su - user` - `apt install screen` - `script /dev/null` - `screen`...

![Image](https://github.com/user-attachments/assets/0a495fbe-6a3a-4882-af0d-cf9ab6f470f0) I received msg `You're bad at computers` But it is completely not true 😛 i am `paranoid spam evader` Keeping DMs opened is too much inviting for spammers. Especially...

New suggestion to fix ``` "You're bad at computers.", "Are you trying to kill me?", "Fat chance.", ``` Just replace/remove this and it should be okay imo

# versions: - registry.terraform.io/hashicorp/aws = 5.0.1 - Terraform v1.4.4 - terragrunt version v0.44.5 # Applying first time (and many times in a row) plan is born ``` # module.stack.module.sandbox_cf.module.cloudfront.aws_cloudfront_distribution.cdn will...

### Continuation of https://github.com/hashicorp/terraform-provider-aws/issues/29234#issuecomment-1567447028 Deployed to production without aws_cloudfront_distribution recreation. Just update in place to solution with `forwarded_values` and revert back via update to using `cache_policy_id` and `origin_request_policy_id` once again...

Update: same bug returned back to staging and production after this solution at some point of time :smiling_face_with_tear: