Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add envs vars for next-build to all tugboat envs #16078

Closed
3 of 5 tasks
tjheffner opened this issue Nov 9, 2023 · 1 comment
Closed
3 of 5 tasks

Add envs vars for next-build to all tugboat envs #16078

tjheffner opened this issue Nov 9, 2023 · 1 comment
Labels
Accelerated Publishing CMS Team CMS Product team that manages both editor exp and devops DevOps CMS team practice area Needs refining Issue status

Comments

@tjheffner
Copy link
Contributor

tjheffner commented Nov 9, 2023

User Story or Problem Statement

For CMS preview functionality with next-build on all tugboat environments, certain environment variables need to be present:

OAUTH_PUBLIC_KEY=
OAUTH_PRIVATE_KEY=
DRUPAL_CLIENT_ID=
DRUPAL_CLIENT_SECRET=

These have been added to the CMS PR environment settings here: https://tugboat.vfs.va.gov/5fd3b8ee7b4657022b5722d6/settings/

They are missing from other CMS tugboat environments, namely the CMS MIRROR project that the next-build repo points to.

AP isn't building next-build on BRD environments yet (though we will need to go to staging in a couple sprints for CMS preview), these same values will need to be added there too.

Description or Additional Context

OAUTH_PUBLIC_KEY= https://us-gov-west-1.console.amazonaws-us-gov.com/systems-manager/parameters/cms/staging/drupal_a[…].key/description?region=us-gov-west-1&tab=Table

OAUTH_PRIVATE_KEY=https://us-gov-west-1.console.amazonaws-us-gov.com/systems-manager/parameters/cms/staging/drupal_a[…].key/description?region=us-gov-west-1&tab=Table

DRUPAL_CLIENT_ID= https://us-gov-west-1.console.amazonaws-us-gov.com/systems-manager/parameters/cms/consumers/next-build/client_secret/description?region=us-gov-west-1&tab=Table#list_parameter_filters=Name:Contains:next-build

DRUPAL_CLIENT_SECRET= https://us-gov-west-1.console.amazonaws-us-gov.com/systems-manager/parameters/cms/consumers/next-build/client_id/description?region=us-gov-west-1&tab=Table#list_parameter_filters=Name:Contains:next-build

slack thread with convo: https://dsva.slack.com/archives/CT4GZBM8F/p1698773025811489
related ticket / PR: #15795 #15936

Steps for Implementation

Add the above environment variables to these (I believe it is these) tugboat settings as well:
https://tugboat.vfs.va.gov/6042eeed6a89945a99399d3d/settings/ < CMS PROD MIRRORS [the environment where next-build repo points to by default is built in this project]
https://tugboat.vfs.va.gov/5ffe2f4dfa1ca136135134f6/settings/ < CMS DEMO ENV
https://tugboat.vfs.va.gov/5fd114f1c65644f68f6376ea/settings/ < CMS-TEST

If it is low-effort to add these variables to the appropriate non-production BRD environments as well, please do so. ❤️

Acceptance Criteria

  • Tugboat environments built under any of the cms projects contain the necessary environment variables

Team

Please check the team(s) that will do this work.

  • CMS Team
  • Public Websites
  • Facilities
  • Accelerated Publishing
@tjheffner tjheffner added Needs refining Issue status Accelerated Publishing Platform CMS Team DevOps CMS team practice area CMS Team CMS Product team that manages both editor exp and devops and removed Platform CMS Team labels Nov 9, 2023
@olivereri
Copy link
Contributor

olivereri commented Nov 9, 2023

  • CMS PR Envs
  • CMS Demo Envs
  • CMS-TEST Pull Request Envs
  • CMS ProdMirrors
  • BRD CMS Staging
  • BRD CMS-test Staging

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accelerated Publishing CMS Team CMS Product team that manages both editor exp and devops DevOps CMS team practice area Needs refining Issue status
Projects
None yet
Development

No branches or pull requests

2 participants