API Reference
Use the API reference after you have chosen a package and workflow. The generated pages list public types, properties, and methods from source so the reference can be refreshed as the SDK changes.
Start with the package guide
| Package | Curated guide | Generated reference |
|---|---|---|
HelmSharp.Action | Package guide | API |
HelmSharp.Chart | Package guide | API |
HelmSharp.Engine | Package guide | API |
HelmSharp.Kube | Package guide | API |
HelmSharp.Release | Package guide | API |
HelmSharp.Repo | Package guide | API |
HelmSharp.Registry | Package guide | API |
HelmSharp.Storage | Package guide | API |
HelmSharp.PostRenderer | Package guide | API |
Reading generated pages
Generated pages intentionally stay factual: type kind, source file, properties, methods, and a short usage note. They do not replace the guide pages because raw member lists cannot explain workflow boundaries.
Template function APIs
Types under HelmSharp.Engine.Functions and HelmSharp.Engine.Utilities are documented as part of the engine reference, but they primarily support Helm/Sprig template execution. Application code should normally call HelmTemplateRenderer, not those helper functions directly.
Regenerating
powershell
pwsh docs/scripts/generate-api-reference.ps1