deef
deef
Oh, I known what happened with the job's container version. I was testing with v3 to see if the helm chart using V3 would work. I exported to a file...
```yml "api": "livenessProbe": "timeoutSeconds": 4 "ingress": "api": "enabled": true "hosts": - "host": "flags.example.com" "paths": - "/" "frontend": "enabled": true "hosts": - "flagsmith.example.com" ``` The issue is that the [env value...
Finally got around to doing the testing I wanted to do. Will get the merge conflicts resolved and mark as ready for review.
Added an example set that goes into a bit of detail on how to use the user-provided templates. The one thing that I was reminded of as I was working...
@jamietanna Is the awaiting reply tag supposed to auto-remove? And or was there anything else you would like me to change about this?
I'll take a look tonight to update the Readme and see if there is anything else I need to do for the docs.
As a side note, these differ from the sprig template functions (see #1536 where sprig is discussed) in parameter ordering. I believe this is to allow pipe-lining easier in the...
Returning an [echo.ErrFoo](https://pkg.go.dev/github.com/labstack/echo/v4#pkg-variables) as the error should properly be unwrapped and the correct response code returned. Not sure if this is the ideal implementation tho as it leaks using echo...
It will pull in _any_ templates provided in the user-templates object. Unfortunately, I did not set it up to have a way to call those templates. As such, you need...
Made the PR ready for review. Could use a check on if the documentation I put in the readme makes sense @sagikazarmark