Documentation for version v0.44.0 is no longer actively maintained. The version you are currently viewing is a static snapshot. For up-to-date documentation, see the latest version.
Annotations
Format ¶
@ann1-name [ann-arg1, ann-arg2, ..., keyword-ann-arg1=val1]
content between brackets is optional.
annotation names are typically namespaced, for example,
overlay/merge
is an annotation within anoverlay
namespace. Annotation namespaces are there for general organization, they are not associated with loaded packages (fromload
keyword).annotation arguments (positional and keyword) is just plain code
Shared templating annotations ¶
@template/code [code]
or just@ [code]
(on its own line) represents plain code line
#@ a = calculate(100)
key: value
@template/value [code]
or just@ [code]
(at the end of line) represents a value associated structure
key: #@ value
array:
- #@ value
YAML templating annotations ¶
@yaml/map-key-override
(no args)- necessary to indicate that map key is being intentionally overriden
@yaml/text-templated-strings
(no args)- necessary to indicate that node contents (including map key and map value) should be text templated (ie
(@
indicates start of text templating) (see text templating for more details.)
- necessary to indicate that node contents (including map key and map value) should be text templated (ie
Text templating annotations ¶
@text/trim-left
trims space to the left of code node@text/trim-right
trims space to the right of code node
Data module annotations ¶
@data/values
(no args) specifies values accessible viadata.values
from@ytt:data
package (see ytt @data/values for more details)
Overlay module annotations ¶
See Overlay module for list of annotations.
(Help improve our docs: edit this page on GitHub)