Albert Heinle

All of them. They were created by searching through the image for configurations inside of it, as well as the Dockerfile which created them. Ideally, these files would be extracted...

They are the configurations inside your image. When you create an image, you would try to ensure that the configurations of the applications running inside are secure. In the case...

Individuals create Docker images and install services inside them. CoGuard_cli found misconfigurations that are not universal, but specific to what is installed inside your image and were misconfigured on your...

Actually, reflecting further on this, the documentation by [Hashicorp](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/kms_grant#encryption_context_subset) is stating that the [encryption_context_subset](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/kms_grant#encryption_context_subset) is supposed to be a list of key value pairs, not a block. This is where...

Last additional comment: I tried two parsers on that file: https://github.com/hashicorp/hcl and https://github.com/amplify-education/python-hcl2 . Both had issues parsing the produced file.

Well... I was posting it here so that it can get attention. For now, I have renamed that resource with some `sed` magic :-)

Well, in order for the terraformer script not to put it as a string, the colons need to be replaced by e.g. underscores

"aws:ebs:id" should be renamed aws_key_id, and remove the quotes (from my example above)

Yes, I am aware that it needs that. But, as you can see from my question, one is in a pickle: Adding `USER nginx` at the end of the Dockerfile...

Well, the underprivileged container has chosen the path of lifting the restrictions of the PID file by putting it into `/tmp` . Anyway, maybe there should be a way to...