agre1981

@pbloigu thank you! your workaround worked for me, regarding permanent fix we can probably use "default" if `name` does not exist

Hello, can we announce official support for java 17? Now documentation says: "We have tested most Grails projects up to JDK 14." https://docs.grails.org/5.2.x/guide/single.html#whatsNew

Yes, you are right, `build` doesn't work in 5.2.5, at least for me ) Looks this relates to the issue: https://github.com/erdi/webdriver-binaries-gradle-plugin/issues/30 ``` Caused by: java.lang.IllegalAccessException: module jdk.proxy4 does not open...

Adding this to dependencies fixes the issue ``` buildscript { dependencies { classpath "org.ysb33r.gradle:grolifant50:2.0.0-alpha.6" } ```

Agree, thanks. Workaround I put here https://github.com/grails/grails-core/issues/12152

Hello @Leodez, great question! There are 2 types of the pattern: **passive view** and **supervising controller** (You can find more information in google). **Supervising controller** uses databinding for communicating with...

Ok, I see, thanks for the explanation. thank you for the application. I love it. Happy holidays!

It doesn't work on sops 3.11.0 (latest) for me. Here is my command: ``` aws sso login --profile dev sops --kms arn:aws:kms:us-east-1:393668382111:key/d0fe3d36-c6b7-4388-bcb2-123456789 --aws-profile "dev" 222.yaml ``` Error: ``` Error encrypting...

According to AWS documentation, they keep sso credentials in `~/.aws/sso/cache/*.json` To get the current sso credentials, we can use ``` aws configure export-credentials --profile sso-profile --format env ```

I found this workaround: ``` eval $(aws configure export-credentials --profile dev --format env) sops edit ./my.sops.yaml ``` or powershell: ``` aws configure export-credentials --profile dev --format powershell | Invoke-Expression ```