Maido
Maido
I created a (probably hacky) fix for it https://github.com/v3rm0n/saml2aws/commit/75a38ee1065ac9f07e04b2310df0715dfd28d762
Example decompilation of Kotlin file `Example.kt`: ``` package some.pkg class Example { fun exampleMethod() {} } fun exampleMethodTopLevel() {} ``` is (with metadata omitted): ``` package some.pkg; public final class...
Meanwhile you can disable autowarm manually and add a custom Terraform file https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lambda_provisioned_concurrency_config EDIT: can't actually use that since the lambda function is not published...
Would you accept a PR that would add a possiblity to add custom Terraform variables e.g: ``` kotless { extensions { terraform { variables = hashMapOf("myvariable" to "value") } }...
Opened PR, locals made more sense https://github.com/JetBrains/kotless/pull/62
Gradle 6.7 is out
Trying to understand this issue to provide more info. Can it be that the other apps use SMC for this? I enumerated all T prefixed values and made a list...
Technically I think they still own the copyright to the code that was made up to the point I forked the repository (I left a company where I started this...
So I'm thinking at minimum there should be a check for COMPLETION_DATE to be NULL so that history does not get changed. Also maybe LIMIT 1 but this is less...
Since AWS Fargate does not copy image labels to the containers, this change would be welcome. Otherwise it's pretty hard to add a git commit sha as a label to...