search

department-of-veterans-affairs / va.gov-vfs-teams

Documentation for External Contractor teams working on the Veteran-facing Services Platform
9 stars 17 forks source link

Updating access request process for VSP #24

Closed b00klegger closed 5 years ago

b00klegger commented 5 years ago

Updating the document to account for a new issue template and repo. Also updated locations on the Internal Tools document.

ricetj commented 5 years ago

~LGTM~

b00klegger commented 5 years ago

@ricetj Do you have write access? Darn it I cannot write to the repo! @wyattwalter Can you write to the repo?

b00klegger commented 5 years ago

@ricetj I opened a companion PR over there for that template this morning 🙂

ricetj commented 5 years ago

@ricetj Do you have write access? Darn it I cannot write to the repo! @wyattwalter Can you write to the repo?

@b00klegger I do not 😞

ricetj commented 5 years ago

@ricetj Do you have write access? Darn it I cannot write to the repo! @wyattwalter Can you write to the repo?

@b00klegger I do not 😞

Nancy is going to give us all access. 🎉

gunsch commented 5 years ago

Looks good! Do we also want to add directions for other tool access here? (Sentry, Grafana, Jenkins, etc.)

b00klegger commented 5 years ago

@gunsch would a parenthetical work better here? When we say 'developer tools' I suppose we mean Grafana, Sentry etc. Perhaps something like:

#### 2. Request that your SSH keys be authorized so that you can use the developer tools such as Grafana, Sentry, Jenkins.

the actual access to the tool is controlled (will be controlled for Sentry) by GitHub OAuth integrations.

gunsch commented 5 years ago

That addition would be nice. How soon is the Sentry / GitHub OAuth integration expected? If it's more than a sprint out, we should probably add directions about that here (i.e. asking for an invite in Slack)