Skip to content

upstream-dependencies.md

Latest commit

 

History

History
75 lines (58 loc) · 11.1 KB

upstream-dependencies.md

File metadata and controls

75 lines (58 loc) · 11.1 KB

Upstream Dependencies

Background

This document lists known external dependencies for the CMS. Official points of contact for each service are listed. Other points of contact for some services are listed on DSVA Slack.

Runtime

Service Content Mode Monitoring Escalation Contact Notes
GovDelivery Situation updates & alerts are sent to subscribed users via GovDelivery Uses govdelivery_bulletins module to post data to the GovDelivery API endpoint See Below https://support.granicus.com/s/contactsupport
Lighthouse Facilities API VAMC, Vet Center, Regional Office, Cemetery, and health services data See Below Nightly Facility Migration; See Below https://valighthouse.statuspage.io #cms-lighthouse slack channel - @facilities-team
Adam Stinton (LH engineer)
VA PO = Michelle Middaugh		 API paths are overridden by settings.php
Lighthouse Forms API Migration imports from VA Forms DB & creates/updates “VA Form” nodes and forms metadata (Form name, dates, PDF filename, status, administration) Nightly Forms Migration https://valighthouse.statuspage.io #va-forms slack channel
@public-websites-team
Github Action (manual & automatically triggered content releases) Editors can trigger a content release either manually or by editing certain content types Calls jenkins webhook http://jenkins.vfs.va.gov/computer/ Ops team (use #vfs-platform-support)
Slack (notifications) Post API failure alerts, Teamsite facility status failure alerts Drupal calls Slack webhook https://status.slack.com/
SSOi (must be on VA network to access doc) CMS users are authenticated with the VA Single Sign On service (SSOi) See [README](https://github.com/department-of-veterans-affairs/va.gov-cms/blob/main/READMES/cms-login.md#technical-details https://iamportal.iam.va.gov/iamv2/index.php (must be on VA network) https://iamportal.iam.va.gov/iamv2/help/contactUs.php (must be on VA network)
Unbound DNS Forwards (and caches) DNS requests from TIC to AWS Route 53 DNS servers Facilitates access to internal services from within network, e.g. CAG access to CMS Datadog synthetic Ops team (use #vfs-platform-support)

GovDelivery

Monitoring

  • Alerting
    • Slack notifications via Datadog from Drupal errors.
  • Error logs
    • /admin/reports/dblog?type%5B%5D=govdelivery_bulletins (ephemeral)
  • Internal
  • External

The following services can affect the CMS's functionality or data at any time.

Lighthouse Facilities API

Content

  • Facility migration README
  • VHA: VAMC & Vet Center Facility metadata and statuses
  • NCA: Cemetery metdata and statuses
  • VBA: Regional Office metadata and statuses
  • Facility services for VAMC, Vet Centers, and Regional Offices

Mode

Build time

The following services can affect the deployment process' ability to fully build the CMS for testing or production deployment.

Service Url Status Escalation Notes
Remi Repo rpms.remirepo.net none Tweet @RemiRepository and open issue at https://forum.remirepo.net/ Remi Repo is used to pull in the PHP 7.3 libraries and dependencies in our AMI builds. This won't be used when we switch from Amazon Linux 1 to Amazon Linux 2 when we move to containers on ArgoKube
Drupal packages packages.drupal.org @drupal_infra on Twitter Drupal packages is used to download Drupal contrib modules
Packagist https://status.packagist.org/ Tweet at @packagist. It is used by thousands of sites so highly likely that someone knows about any issues before we do and that it will be resolved quickly. Packagist is used to install our PHP dependencies that are required by Drupal custom and contrib modules.
Github https://www.githubstatus.com/ Use the #github_information channel in DSVA slack The codebase is stored in github, and the deployment process depends on it to pull code and push status and code quality messages to our pull requests.
ZenHub https://twitter.com/zenhubstatus ZenHub is a project management layer on top of GitHub Issues that we use.
Docker Hub https://status.docker.com/ Contact support@docker.com and/or tweet @Docker We use Docker Hub to pull down container images for our CI environments in Tugboat.

Composer

There are a number of services that Composer uses to download and install dependencies. These services are used during the build process and are not required for runtime.