Juho Saarinen

Code that cause the issue also at Azure/terraform-azurerm-avm-res-containerregistry-registry#76

Init empty project with typescript with CDKTF cdktf.json: ```json { "language": "typescript", "app": "npx ts-node main.ts", "projectId": "a24002df-12f0-46e1-9d08-9cfcb038742f", "sendCrashReports": "false", "terraformProviders": [], "terraformModules": [ "Azure/avm-res-storage-storageaccount/[email protected]" ], "context": { } }...

We use Artifactory as state backend, I understood that `Cloud` backend is reserved for HCP Terraform (ex-Terraform Cloud) (and it's Enterprise version) and `remote` is for that

I agree to change the license from Commons-Clause v1.0 to Apache-2.0

Maybe this could be typed also on construct side. I had similar thing included to other PR (https://github.com/cdklabs/cdk-ecr-deployment/commit/1eebc0c4695eff3e95e62fbca84519ed2aaf8a60#diff-c54113cf61ec99691748a3890bfbeb00e10efb3f0a76f03a0fd9ec49072e410aR98-R110), but removed it already from there as it's easily creating breaking change....

It might be that whole resource should be ephemeral, or then ID should be hash as now it has also Customer key as plain text.

Implemented partially logic to handle `nil`s in code (e.g. due to JSON facts with relaxed schema). Handled already "normal" operators and also e.g. string function calls for left hand side...

True, it's easier to keep the default as-is for now, but still it would be nice to be able to enable user namespace usage directly from chart. As mentioned, this...

@air-hand it's not that straight forward, as the docs you pasted still have `privileged: true` set. So even it partially works at user namespace, container still has privileges also on...

I just closed the PR, as failed to see earlier that `template.spec` already passes through so that with current version it's already possible to set `template.spec.hostUsers: false` and get runner...