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
curl is a client. The builders draft a command or a snippet from choices you type. The URL is a service you administer, or a public documentation host such as example.com that you are not trying to load. One request.
A header that contains a token is a secret. prompt-for-this stays in the saved command. The real token stays in the store. A command in the shell history is a copy. Remove it if a token slipped in.
Do not loop the request. Do not point it at a site to knock it over. A status code is the result you write down.
Converting the command to code is a draft for a developer. It is not a deployment.
The change you can finish
Apply nothing during the writing of the note. When the lab window opens, it is one change on the device named in the ticket. Read the draft, then the device, then decide.
Rollback is the file or the revision you saved first. You do not invent a rollback after the only copy is gone.
- Name the URL you may request.
- Draft one command.
- Remove tokens.
- Send one request in the lab window, or none in the writing hour.
- Write the status.
- Clear a secret from history if one appeared.
Mistakes that outlive the command
curl for Network Admins goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- A token in the ticket.
- A loop.
- A target you do not have reason to request.
- example.com left in a production script.
- A generated code snippet deployed unread.
Decisions to write down
One decision for curl for Network Admins: The URL is allowed. The saved command has no token. One request. The status is written. And history is clean of secrets.
Checks before you call it done
Confirm this before you call the change done: The status is in the ticket. The command in the note has no secret. No loop ran. The host is yours or a documented example you did not hammer. And code conversion was not deployed. If one of those fails, stop.
One request. No token in the note.
prompt-for-this marks the header.Before you leave the device
curl for Network Admins ends when the hostname on the device matches the hostname in the ticket. If it does not, you are on the wrong box. Stop. A command that succeeded on the wrong box is not progress.
The draft stays a draft until a person has read the names in it. A generator does not log into the device and does not know which interface is the uplink. You delete a line that names a device, a zone, or a prefix you did not write down.
0.0.0.0/0 is not kept because a sample included it. A source you can say is the source you keep. 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. They belong in the note. They are not prefixes you type onto a production device because they appeared in a draft.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, a community string, or a pre-shared key you save in the ticket or in git. The real secret stays in the store.
One change is the window. A VLAN and a routing protocol and a VPN do not share it. If two things move and the result is wrong, you will not know which one did it. The next feature waits for its own page.
If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied config produces a device nobody can rebuild. Restore the copy you took first.
A second person reads the device name and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the device alone.
This page is a planning guide. It is not a vendor manual, not an official standard, and not a permission to touch a network you do not administer. The pillar guide owns the wider design. This page owns one lab proof.
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.