jeho

Yes, and please do not print the `Usage` sting if provided file has invalid content. The `Usage` string should be only printed if a command arguments are invalid or missing.

sure, annotation allows to integrate with underlining platform/cloud provider. In my particular case, I added annotation to mitigate issue with policy that disallows `non-semver` tag. If I recall it correctly...

@anttiviljami The OpenApiV3 is relatively new and there is a huge number of existing API in version 2. I would be eager to contribute to this project, as I see...

It turned out that my terminal adds backslashes after pasting command ``` wget -q https://github.com/noqcks/gucci/releases/download/${VERSION}/gucci-v${VERSION}-darwin-amd64 ``` Terminal adds backslashes: ``` wget -q https://github.com/noqcks/gucci/releases/download/$\{VERSION\}/gucci-v$\{VERSION\}-darwin-amd64 ``` Adding quotes around url solves that...

Perhaps we could rename the `Otomi-welcome` secret to `do-not-remove-me` or `keep-me-always`.

UI proposal 

exactly

Hi, I see very interesting conversation here and I would like to put my two cents. First of all, I think that using `sub` scope for user identification is quite...

Would it be possible implement third argument for `sprig htpasswd`, so I can provide htpasswd related arguments? e.g.: ``` {{ htpasswd .Values.username .Values.password 'nBC 10' }} ```

fixed