You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 1908e4e
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: .about.yml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ project: "api.data.gov"
3
3
full_name: api.data.gov
4
4
name: api-data-gov
5
5
github:
6
-
- 18F/api.data.gov
6
+
- GSA/api.data.gov
7
7
- NREL/api-umbrella
8
8
description: "A hosted, shared-service that provides an API key, analytics, and proxy solution for government web services. We are currently accepting clients for this free service: contact us to learn more."
[https://api.data.gov](https://api.data.gov/) is a free API management service for federal agencies. Our aim is to make it easier for agencies to release and manage APIs.
6
6
7
-
-[Program Notes for api.data.gov](https://github.com/18F/api.data.gov/wiki/Program-Notes)
7
+
-[Program Notes for api.data.gov](https://github.com/GSA/api.data.gov/wiki/Program-Notes)
8
8
-[GitHub Repository for API Umbrella](https://github.com/NREL/api-umbrella), the underlying technology of `api.data.gov`
9
9
10
10
## Notes
@@ -31,7 +31,7 @@ After you're happy with your changes, commit and submit a pull request.
31
31
32
32
## Deploy
33
33
34
-
Changes pushed to `main` should automatically be published to production within a few minutes via the [CI GitHub Action](https://github.com/18F/api.data.gov/actions/workflows/main.yml).
34
+
Changes pushed to `main` should automatically be published to production within a few minutes via the [CI GitHub Action](https://github.com/GSA/api.data.gov/actions/workflows/main.yml).
4. Navigate to the webpage where you placed the snippet. You should see a signup form and be able to signup for an API key completely on your own site. Run into any issues? [File an issue](https://github.com/18F/api.data.gov/issues).
377
+
4. Navigate to the webpage where you placed the snippet. You should see a signup form and be able to signup for an API key completely on your own site. Run into any issues? [File an issue](https://github.com/GSA/api.data.gov/issues).
378
378
379
379
## Linking to your own contact/support address
380
380
@@ -439,7 +439,7 @@ Everything you can do within the api.data.gov admin interface is powered by an A
439
439
440
440
## How to post an alert box on api.data.gov and on the individual documentation pages to notify users of upcoming status changes.
441
441
442
-
Edit the source of your documentation page (for example, [source/docs/nrel/index.md.erb](https://github.com/18F/api.data.gov/blob/main/source/docs/nrel/index.md.erb)). Add a snippet like this to the top of the page below the front-matter (below the last `---` line):
442
+
Edit the source of your documentation page (for example, [source/docs/nrel/index.md.erb](https://github.com/GSA/api.data.gov/blob/main/source/docs/nrel/index.md.erb)). Add a snippet like this to the top of the page below the front-matter (below the last `---` line):
Copy file name to clipboardExpand all lines: docs/procedures.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,11 +4,11 @@ This document is to memorialize internal project procedures. Other agencies or t
4
4
5
5
##### api.data.gov
6
6
7
-
The System owner and current project developers need commit rights to api.data.gov project repositories ([here](https://github.com/18F/api.data.gov) and [here](https://github.com/18F/api.data.gov-ops). The system owner (currently Gray Brooks) manages this access, granting access to new project developers when they come onboard and removing access when they leave.
7
+
The System owner and current project developers need commit rights to api.data.gov project repositories ([here](https://github.com/GSA/api.data.gov) and [here](https://github.com/GSA/api.data.gov-ops). The system owner (currently Gray Brooks) manages this access, granting access to new project developers when they come onboard and removing access when they leave.
8
8
9
9
Specifically, current developers are managed as the `api.data.gov` team in the 18F GitHub organization.
10
10
11
-
Both of the adding and removing processes should be initiated by creating an issue in the project's [issue tracker](https://github.com/18F/api.data.gov/issues). Any one can create the issue, but the system owner should be the one who addresses and closes it.
11
+
Both of the adding and removing processes should be initiated by creating an issue in the project's [issue tracker](https://github.com/GSA/api.data.gov/issues). Any one can create the issue, but the system owner should be the one who addresses and closes it.
12
12
13
13
These accounts are created for developers that need access to contribute code and deploy apps.
14
14
@@ -26,11 +26,11 @@ For the api.data.gov service, we utilize [a public, opensource project](https://
26
26
27
27
The System owner and current project developers need application admin rights within the [api.data.gov system](https://api.data.gov/admin). The system owner (currently Gray Brooks) manages this access, granting access to new project developers when they come onboard and removing access when they leave.
28
28
29
-
Both of the adding and removing processes should be initiated by creating an issue in the project's [issue tracker](https://github.com/18F/api.data.gov/issues). Any one can create the issue, but the system owner should be the one who addresses and closes it.
29
+
Both of the adding and removing processes should be initiated by creating an issue in the project's [issue tracker](https://github.com/GSA/api.data.gov/issues). Any one can create the issue, but the system owner should be the one who addresses and closes it.
30
30
31
31
These accounts are created for developers that need access to view system data across all participating APIs and to help set up and manage agency access to the system.
32
32
33
-
1. Create an issue in the project's [issue tracker](https://github.com/18F/api.data.gov/issues) to track the request.
33
+
1. Create an issue in the project's [issue tracker](https://github.com/GSA/api.data.gov/issues) to track the request.
34
34
2. The system owner, currently Gray Brooks, should see and respond to it. If there's any urgency, contact him via Slack or Email.
35
35
3. The system owner will confirm the GSA identity of the applicant, and signal approval in the ticket.
36
36
4. The system owner will then create the api.data.gov admin account for the new member, grant them the appropriate permissions, and close the ticket.
@@ -41,7 +41,7 @@ Agency contacts need api.data.gov accounts in order to view the api key users an
41
41
42
42
The adding process should be initiated by creating an issue in the project's [ops issue tracker](https://github.com/18f/api.data.gov-ops/issues). Any one can create the issue, but the system owner should be the one who addresses and closes it.
43
43
44
-
1. Create an issue in the project's [issue tracker](https://github.com/18F/api.data.gov/issues) to track the request.
44
+
1. Create an issue in the project's [issue tracker](https://github.com/GSA/api.data.gov/issues) to track the request.
45
45
2. The system owner, currently Gray Brooks, should see and respond to it. If there's any urgency, contact him via Slack or Email.
46
46
3. The system owner will confirm the agency identity of the applicant, and signal approval in the ticket.
47
47
4. The system owner will then create the api.data.gov admin account for the new members, grant them the appropriate permissions, and close the ticket.
@@ -52,11 +52,11 @@ The System owner and current project developers need cloud.gov access to api.dat
52
52
53
53
Specifically, current developers are [granted](https://cloud.gov/docs/apps/managing-teammates/) OrgManager rights to `gsa-tts-api-data-gov`.
54
54
55
-
Both of the adding and removing processes should be initiated by creating an issue in the project's [issue tracker](https://github.com/18F/api.data.gov/issues). Any one can create the issue, but the system owner should be the one who addresses and closes it.
55
+
Both of the adding and removing processes should be initiated by creating an issue in the project's [issue tracker](https://github.com/GSA/api.data.gov/issues). Any one can create the issue, but the system owner should be the one who addresses and closes it.
56
56
57
57
These accounts are created for developers that need access to contribute code and debug apps.
58
58
59
-
1. Create an issue in the project's [issue tracker](https://github.com/18F/api.data.gov/issues) to track the request.
59
+
1. Create an issue in the project's [issue tracker](https://github.com/GSA/api.data.gov/issues) to track the request.
60
60
61
61
1.[Create an account]() with cloud.gov and this will include multi factor authentication with [Google authenticator](https://support.google.com/accounts/answer/1066447?hl=en) or [authy](https://www.authy.com/).
62
62
@@ -72,11 +72,11 @@ The System owner and current project developers need cloud.gov access to api.dat
72
72
73
73
Specifically, current developers are [granted](http://docs.aws.amazon.com/IAM/latest/UserGuide/id_users.html)`Developer` rights to the `apidatagov` AWS account.
74
74
75
-
Both of the adding and removing processes should be initiated by creating an issue in the project's [issue tracker](https://github.com/18F/api.data.gov/issues). Any one can create the issue, but the system owner should be the one who addresses and closes it.
75
+
Both of the adding and removing processes should be initiated by creating an issue in the project's [issue tracker](https://github.com/GSA/api.data.gov/issues). Any one can create the issue, but the system owner should be the one who addresses and closes it.
76
76
77
77
These accounts are created for developers that need access to contribute code and debug apps.
78
78
79
-
1. Create an issue in the project's [issue tracker](https://github.com/18F/api.data.gov/issues) to track the request.
79
+
1. Create an issue in the project's [issue tracker](https://github.com/GSA/api.data.gov/issues) to track the request.
80
80
81
81
2. The system owner will confirm the GSA identity of the applicant and comment on the ticket to show approval.
82
82
@@ -98,7 +98,7 @@ The development team checks for security events weekly. Any unusual or suspiciou
98
98
99
99
Checklist:
100
100
101
-
1. Create an issue in the project's [issue tracker](https://github.com/18F/api.data.gov/issues) to track this Security Event Review.
101
+
1. Create an issue in the project's [issue tracker](https://github.com/GSA/api.data.gov/issues) to track this Security Event Review.
102
102
2. Review tool for all repositories and open a ticket for all "red" alerts.
103
103
3. Review [production logs](https://logs.fr.cloud.gov) for unapproved and unusual activities.
104
104
4. Review actionable security events on production logs for successful and unsuccessful account logon events, account management events, object access, policy change, privilege functions, process tracking, system events, all administrator activity, authentication checks, authorization checks, data deletions, data access, data changes, and permission changes.
0 commit comments