This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
Azure Pipelines YAML Cheat Sheet is a reading list for Azure Pipelines. The generator drafts one pipeline and says to review it before you enable it. Secrets stay in the platform secret store.
A job that prints a secret, disables branch protection, or applies with auto-approve is a line you delete. The sample image ghcr.io/example/app:latest is replaced.
The browser tool drafts text. It does not run the job.
192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. A sample password is replaced. It is not a password you keep. 10.0.0.0/16 is a sample prefix, not a network you publish unless you already use it.
The change you can finish
Apply nothing while you are writing the note. When the lab window opens, it is one change on the account named in the ticket. Read the draft, then the account, then decide.
Rollback is the previous file, the previous plan, or the lab resource you can delete because it was only a lab.
- Confirm the repository you administer.
- Read one job the ticket names.
- Delete a printed secret or auto-approve.
- Do not enable a workflow from this sheet.
- Hand a new pipeline to the how-to for that example.
- Stop.
Mistakes that outlive the statement
Azure Pipelines YAML goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- Applying a draft you did not read.
- The wrong account.
- A secret, an access key, or a kubeconfig in git.
- Two changes in one window.
- No copy saved before the change.
- A documentation address or example.com left in a file you apply.
- An ingress from 0.0.0.0/0 left in the file.
- Calling the generator output a finished production change.
- A workflow enabled because the YAML was short.
- auto-approve left in the file.
Decisions to write down
One decision for Azure Pipelines YAML: This sheet is for reading. The forge is Azure Pipelines. Secrets stay in the secret store. No workflow was enabled. And the how-to owns any new pipeline.
Checks before you call it done
Confirm this before you call the change done: The repository is written. One job was read. No secret is in the note. Nothing was enabled. And the next action is a named how-to, or a stop. If one of those fails, stop.
# Read first. Enable later, from the how-to.
# Azure Pipelines.
# Review before you enable this.
# 192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. A sample password is replaced. It is not a password you keep. 10.0.0.0/16 is a sample prefix, not a network you publish unless you already use it.Before you leave the account
Azure Pipelines YAML Cheat Sheet ends when the account in the note is the account in the ticket. If it is not, stop.
The draft stays a draft until a person has read the names in it. A generator does not log in, does not apply, and does not scan.
192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. A sample password is replaced. It is not a password you keep. 10.0.0.0/16 is a sample prefix, not a network you publish unless you already use it.
prompt-for-this is a reminder that a secret is missing. It is not an access key, a token, or a password you save. An Azure secret draft may contain a sample password. Replace it. Do not file it.
One change is the window. If two things move and the result is wrong, you will not know which one did it.
If the same step fails twice, stop for the day. Restore the copy you took first.
A second person reads the account and the change aloud. If they cannot find them in the ticket, the note is not done.
This page is a planning guide. It is not a vendor manual, not an official standard, not legal advice, and not an audit opinion. You do not apply it against an account you do not administer.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.