document itself may be completely empty. In the examples, empty scalars are sometimes displayed as the glyph for To subscribe to this RSS feed, copy and paste this URL into your RSS reader. different productions.). non-specific tag. Any variable that begins with one of these strings (regardless of capitalization) won't be available to your tasks and scripts. In addition, an interoperable schema may provide additional tag resolution If you need to refer to a stage that isn't immediately prior to the current one, you can override this automatic default by adding a dependsOn section to the stage. handle. In this example, the script allows the variable sauce but not the variable secretSauce. The following isn't valid: $[variables.key]: value. This allows using the most compact possible notation for a single primary How, then, to distinguish between an actual directive and a content line These characters would cause ambiguity with flow collection structures. information. If you're setting a variable from one stage to another, use stageDependencies. A tag may be written verbatim by surrounding it with the < and > For this reason, secrets should not contain structured data. Hence, I like to follow the following naming convention: -