55037 set output deprecation (#58494)

* Automatic updates for gh-actions * Update references to gh-actions --------- Co-authored-by: Christopher Floess <[email protected]>
department-of-veterans-affairs · May 19, 2023 · 491d599 · 491d599
1 parent cd089dc
commit 491d599
Show file tree

Hide file tree

Showing 4 changed files with 10 additions and 3 deletions.
diff --git a/.github/ISSUE_TEMPLATE/offboarding-request.md b/.github/ISSUE_TEMPLATE/offboarding-request.md
@@ -49,7 +49,7 @@ _The following steps are performed by the **Platform Support** team. Detailed in
  - [ ] AWS Access removed  (if applicable. Search their name in [AWS IAM](https://console.amazonaws-us-gov.com/iamv2/home#/home))
    > Use the [Remove SOCKS and AWS access Github Workflow](https://github.com/department-of-veterans-affairs/devops/actions/workflows/offboarding.yml) to remove user's entry from DSVA AWS. You'll need the user's AWS username (typically `First.Last`).
  - [ ] User removed from the VA GitHub Org (if applicable. Check [department-of-veterans-affairs/people](https://github.com/orgs/department-of-veterans-affairs/people))
-   > Fill out request found [here](https://github.com/department-of-veterans-affairs/github-user-requests/issues/new?assignees=&labels=remove-user&template=user-remove.yml&title=Remove+User+from+Org%3A+%5Busername%5D). 
+   > Fill out request found [here](https://github.com/department-of-veterans-affairs/github-user-requests/issues/new?assignees=&labels=remove-user&template=user-remove.yml&title=Remove+User+from+Org%3A+%5Busername%5D).
  - [ ] Pagerduty access removed (if applicable. Check [pd users](https://dsva.pagerduty.com/users-new))
  - [ ] [Okta account](https://vfs.atlassian.net/wiki/spaces/OT/pages/2532508159/Offboarding+users+from+Okta) disabled (if applicable)
  - [ ] [Datadog account](https://vfs.atlassian.net/wiki/spaces/OT/pages/2526282894/Offboarding+Users+from+Datadog) disabled (if applicable. Check [Datadog users](https://vagov.ddog-gov.com/organization-settings/users))

diff --git a/.github/dependabot.yml b/.github/dependabot.yml
@@ -0,0 +1,7 @@
+version: 2
+updates:
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      # Check for updates to GitHub Actions every week
+      interval: "weekly"
diff --git a/products/facilities/mapbox/README.md b/products/facilities/mapbox/README.md
@@ -21,7 +21,7 @@ So, the process by which the keys are fetched from AWS Parameter Store and ultim
 1. Fetch from AWS Parameter Store in required workflows (e.g. [continuous-integration](https://github.com/department-of-veterans-affairs/vets-website/blob/8de1ed2fa5b6a462323c2c482e6e2115ac666556/.github/workflows/continuous-integration.yml#L61), [e2e-tests](https://github.com/department-of-veterans-affairs/vets-website/blob/8de1ed2fa5b6a462323c2c482e6e2115ac666556/.github/workflows/e2e-tests.yml#L104))
 ```
       - name: Get Mapbox Token
-        uses: marvinpinto/action-inject-ssm-secrets@v1.2.1
+        uses: department-of-veterans-affairs/action-inject-ssm-secrets@d8e6de3bde4dd728c9d732baef58b3c854b8c4bb # latest
         with:
           ssm_parameter: /dsva-vagov/vets-website/dev/mapbox_token
           env_variable_name: MAPBOX_TOKEN

diff --git a/products/identity/Mocked Authentication/Mockdata/sync.md b/products/identity/Mocked Authentication/Mockdata/sync.md
@@ -14,7 +14,7 @@ The key is stored in parameter store -  `/dsva-vagov/vets-api/staging/mockdata_s
 
 #### Inject the api_key into the workflow:
 ```yml
-- uses: marvinpinto/action-inject-ssm-secrets@v1.1.1
+- uses: department-of-veterans-affairs/action-inject-ssm-secrets@d8e6de3bde4dd728c9d732baef58b3c854b8c4bb # latest
   with:
     ssm_parameter: /dsva-vagov/vets-api/staging/mockdata_sync_api_key
     env_variable_name: MOCKDATA_API_KEY