Merge branch 'main' into VACMS-18005-aging-content-tests

.github/ISSUE_TEMPLATE/runbook-facility-url-change.md

@@ -6,6 +6,8 @@ labels: Facilities, Drupal engineering, Flagged Facilities, Redirect request, UR
 assignees: ''
 
 ---
+Parent ticket: #number-of-GH-ticket
+
 ### Implementation date
 When does this request need to be live:
 [MM/DD/YYYY]

.github/ISSUE_TEMPLATE/runbook-vamc-facility-closed.md

@@ -58,7 +58,7 @@ If this facility has been removed from VAST in error, please notify the VA Drupa
 [outro]
 
 [CMS helpdesk signature]
-   
+
 Alternative, for "Removed From Source" flag follow-up:
 -----------------------
 During a site-wide review, our team found a location within the [INSERT SYSTEM NAME] health care system that is no longer listed within the Facilities API, but still exists within Drupal.
@@ -69,26 +69,26 @@ Here is a link to the clinic homepage, which is still published on the live site
 
 Here is a link to this page on the production site:  [INSERT CLINIC HOMEPAGE LINK FROM PRODUCTION SITE]
 
-IF THIS FACILITY IS CLOSED: 
+IF THIS FACILITY IS CLOSED:
 Please follow the steps listed in the following Knowledge Base article in order to fully archive it from VA.gov: https://prod.cms.va.gov/help/vamc/about-locations-content-for-vamcs/how-to-archive-a-closed-facility
 
-Important: Once these steps have been followed, please reach back out to the VA Drupal CMS Help Desk by replying to this email or by writing to [email protected]. 
+Important: Once these steps have been followed, please reach back out to the VA Drupal CMS Help Desk by replying to this email or by writing to [email protected].
 
 From there, our engineering team will proceed with next steps for archiving this facility.
 
 If the clinic has not been closed, please also let our team know as soon as possible.
 
 Thank you for your help!
-   
+
 [Signature]
-   
+
 ```
 </details>
 
 - [ ] 4. Are any of the services or upcoming events for the facility to be closed moving to a different facility?
   - [ ] 4a. If so, note the facility picking up the services and events here: <insert_target_facility>
   - [ ] 4b. If so, note the services and events here: <insert_services_to_be_moved>
-- [ ] 5. Create a [redirect request](https://github.com/department-of-veterans-affairs/va.gov-cms/issues/new?assignees=&labels=Redirect+request&template=redirect-request-facility-url.md&title=Redirect+Request+for%3A+%3Cinsert+facility+name%3E) from the URL of the facility to be closed to the URL of its parent system.
+- [ ] 5. Create a [URL change](https://github.com/department-of-veterans-affairs/va.gov-cms/issues/new?assignees=&template=runbook-facility-url-change.md&title=URL+Change+for%3A+%3Cinsert+facility+name%3E) to redirect the from the URL of the facility to be closed to the URL of its parent system and to remove the old canonical link.
 
 <insert_redirect_request_link>
 

.github/ISSUE_TEMPLATE/runbook-vamc-facility-new.md

@@ -61,8 +61,6 @@ Please let us know when your draft content is complete, so that we can wrap up t
 #### CMS engineer steps
 - [ ] 7. CMS engineer executes the steps of the URL change request ticket from step 5 above.
 
-(Redirects deploy daily except Friday at 10am ET, or by requesting OOB deploy (of the revproxy job to prod) in #vfs-platform-support. Coordinate the items below and canonical URL change after URL change ticket is merged, deployed, and verified in prod.)
-
 #### Drupal Admin steps (CMS Engineer or Help desk)
 _Help desk will complete these steps or escalate to request help from CMS engineering._
 - [ ] 8. Drupal Admin bulk publishes nodes and facility.

.github/ISSUE_TEMPLATE/runbook-vet-center-closed.md

@@ -17,7 +17,7 @@ Help desk ticket: <insert_help_desk_link>
 - [ ] Name of submitter (if applicable)
 Submitter: <insert_name>
 
-- [ ] Contact the Vet Center editor and send them a link to the operating status KB article. If the facility has not closed yet and we can provide lead-time, the editor should change the Facility status to "Facility notice" and provide information in the Facility Status additional information about when the facility will permanently close.  
+- [ ] Contact the Vet Center editor and send them a link to the operating status KB article. If the facility has not closed yet and we can provide lead-time, the editor should change the Facility status to "Facility notice" and provide information in the Facility Status additional information about when the facility will permanently close.
 - [ ] When the facility has already closed - including if we were unable to give the aforementioned lead time- the editor should change the Facility status to Closed and provide information in the Facility Status additional information that the facility has permanently closed as of DATE.
    - Vet Center Mobile autoarchive when they are removed from the facilty API.  No action required.
    - Vet Center Outstations autoarchive when they are removed from the facilty API.  No action required.
@@ -41,7 +41,7 @@ Facility API ID: <insert_facility_API_ID>
 #### CMS help desk steps
 **Note: If the help desk is waiting on information from the facility staff or editor, add the "Awaiting editor" flag to the facility with a log message that includes a link to this ticket. Remove the flag when the ticket is ready to be worked by the Facilities team. Be sure to preserve the current moderation state of the node when adding or removing the flag.**
 - [ ] 1. Become aware that the facility is no longer on the Facility API (typically, via a Flag, but this may come in as a helpdesk ticket).
-- [ ] 2. ~~CMS team submits [Redirect request](https://github.com/department-of-veterans-affairs/va.gov-cms/issues/new?assignees=&labels=Redirect+request&template=redirect-request-facility-url.md&title=Redirect+Request+for%3A+%3Cinsert+facility+name%3E), cc'ing Facilities team, and referencing this issue.~~ redirects are not necessary for Outstations.
+- [ ] 2. ~~Create a [URL change](https://github.com/department-of-veterans-affairs/va.gov-cms/issues/new?assignees=&template=runbook-facility-url-change.md&title=URL+Change+for%3A+%3Cinsert+facility+name%3E) to redirect the from the URL of the facility to be closed to the URL of its parent system and to remove the old canonical link.~~ redirects are not necessary for Outstations.
 
 #### Drupal Admin steps (CMS Engineer or Help desk)
 _Help desk will complete these steps or escalate to request help from CMS engineering._

READMES/events-api

@@ -3,8 +3,11 @@ Directions for Events API
 This is a REST API created in Drupal Views using the REST UI Module. It is located in the Drupal CMS backend and is administered by the CMS team.
 
 The current location to view the API is: /all-events-data?_format=json
+You can view it using an API platform (like Postman). 
+You will need a Drupal login (username and password). Under Basic Auth you will enter the full url - https://prod.cms.va.gov/all-events-data?_format=json and the username/password combo.
+This will allow you to view the full events API data.
 
-The API is currently set to json format but can also be used for xml or to get a csv download. This is accomplished by changing the data_format in the url above. (I.e. /all-events-data_format=csv or  /all-events-data_format=xml)
+The API is currently set to json format but can also be used for xml or to get a csv download. This is accomplished by changing the data?_format in the url above. (I.e. /all-events-data?_format=csv or  /all-events-data?_format=xml)
 
 To make changes to the Events API in the Drupal Admin you can go to /admin/structure/views/view/events_data. Any changes made to this API require an export of Drupal config so please consult with (and have your changes reviewed by) a Drupal CMS Developer.
 

config/sync/views.view.events_data.yml

@@ -14,7 +14,7 @@ dependencies:
     - field.storage.node.field_location_type
     - field.storage.node.field_url_of_an_online_event
     - node.type.event
-    - user.role.administrator
+    - user.role.authenticated
   module:
     - address
     - csv_serialization
@@ -766,7 +766,7 @@ display:
         type: role
         options:
           role:
-            administrator: administrator
+            authenticated: authenticated
       cache:
         type: tag
         options: {  }
@@ -895,7 +895,8 @@ display:
         jsonapi_views:
           enabled: true
       path: all-events-data
-      auth: {  }
+      auth:
+        - basic_auth
     cache_metadata:
       max-age: -1
       contexts: