Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document how to use of go-template custom func or external library (sprig) functions #20

Open
pixelsoccupied opened this issue May 28, 2024 · 6 comments
Labels
kind/documentation Categorizes issue or PR as related to documentation. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@pixelsoccupied
Copy link
Contributor

pixelsoccupied commented May 28, 2024

https://masterminds.github.io/sprig/

@nocturnalastro
Copy link
Contributor

Could move the custom functions into there own package and then link from the docs to the page on https://pkg.go.dev

@pixelsoccupied pixelsoccupied changed the title Document use of custom or external library go template functions Document how to use of go-template custom func or external library (sprig) functions Jun 4, 2024
@pixelsoccupied
Copy link
Contributor Author

pixelsoccupied commented Jun 4, 2024

@nocturnalastro sorry just update the title to make it a bit more clear.

We have imported Sprig as one of the dependencies which allows us to use funcs like has to test if an element is persent etc....was thinking if it can be documented

Also we can have custom func written in go-template contained with a CR (a.k.a template function) to validate stuff further

@pixelsoccupied
Copy link
Contributor Author

pixelsoccupied commented Jun 4, 2024

Could move the custom functions into there own package and then link from the docs to the page on https://pkg.go.dev/

But that's a good idea!

@pixelsoccupied
Copy link
Contributor Author

/documentation

@openshift-ci openshift-ci bot added the kind/documentation Categorizes issue or PR as related to documentation. label Jun 11, 2024
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 10, 2024
@nocturnalastro
Copy link
Contributor

/lifecycle frozen

@openshift-ci openshift-ci bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Categorizes issue or PR as related to documentation. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

3 participants