janearc
commented
9 years ago From noah in email 15 Dec 14 (mostly verbatim):
My intention was for the scheme to be easy and communicative. When looking around at current documentation to link back to actual budgetary authorities, I saw things like 701.15.TUHS3600.UH02.25.UH360.K50 or 285X.A0010100.AF10.11.003.
Clearly, that was not going to work.
Parsing through our IAA 7600Bs (which then trackback to our 7600As), and OMB Codes parsed by the great Sean Herron, I've whipped together the following UID format:
AgencyAcronym-StartDateInYYYYMMDD-EndDateInYYYYMMDD-##
For example:
FEC-20141001-20150915-001
The acronym is determined by agency, not department. For example, we'd use CIS instead of DHS. CIS implies DHS, so no need to repeat ourselves. Yet the reverse doesn't tell us where the money is actually coming from.
The dates are determined by your IAA 7600B. If you're not sure what those are, check out the Agreement folders in Google Drive and check with your Product Lead. Initially, I will be validating, and generating the canonical list, which will be available for your use starting Monday.
Effective immediately, the first system we will be deploying this on will be AWS. I'll be working this weekend to:
- update AWS onboarding documentation
- bring current AWS resources under this regime
- getting the standard itself to GitHub for PRs and Issues and cross-link from applicable documentation
Going forward all resources that accept tags in AWS must have the following:
key = client value = AgencyAcronym-StartDateInYYYYMMDD-EndDateInYYYYMMDD-##
FAQs
- Why is the AWS key client instead of partner?
Because it is not a 1:1 relationship. For example, the main partner for FOIA is Department of Justice, with assist from OSTP. But the one paying the $ is GSA OCSIT.
- Can I use these codes on other systems besides AWS?
Yes! Do so immediately, if they accept such a parameter. Thank you!
- Why no reference to the project/product/service/team name?
As we recently saw with Mirage, these names can change and suddenly. We actually want that flexibility. But the movement of money should be canonical and unique.
- Why bother with dates?
Beyond helping with uniqueness, it is important that we incur no costs outside a period of performance. Long before an IAA expires, we need a sunset plan or a new IAA. This will help us script alerts in the future.
A function to parse the AWS "name" field as described by Noah is required because we will be launching instances.