-
Notifications
You must be signed in to change notification settings - Fork 70
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
VACMS-15798 / 15791 / 15795 next preview configs + oauth key handling #15936
Conversation
Bumps [datadog/dd-trace](https://github.com/DataDog/dd-trace-php) from 0.92.2 to 0.93.1. - [Release notes](https://github.com/DataDog/dd-trace-php/releases) - [Commits](DataDog/dd-trace-php@0.92.2...0.93.1) --- updated-dependencies: - dependency-name: datadog/dd-trace dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* VACMS-14342: Set up CODEOWNERS * h/t Dave * h/t Tanner * h/t Dave * Update .github/CODEOWNERS * Apply suggestions from code review h/t @swirtSJW
Bumps [va-gov/content-build](https://github.com/department-of-veterans-affairs/content-build) from 0.0.3377 to 0.0.3378. - [Release notes](https://github.com/department-of-veterans-affairs/content-build/releases) - [Commits](department-of-veterans-affairs/content-build@v0.0.3377...v0.0.3378) --- updated-dependencies: - dependency-name: va-gov/content-build dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* VACMS-15276: Adds YouTube field * VACMS-15276: Adding field storage for YouTube
…Filter (#15896) * VACMS-15891: Update workflow filter to multiple * VACMS-15891: Updated the filter machine name too because Jill is smart. * VACMS-15891: Style-Guide-Related edits to view * VACMS-15891: Added section filter * VACMS-15891: Fix caption * VACMS-15891: Caption and tab * VACMS-15891: Copying new settings from view family * VACMS-15891: Fix pager back to 25 for cypress test
id: next_build_preview_server | ||
label: 'Next Build Preview Server' | ||
base_url: 'http://localhost:3000' | ||
preview_url: 'http://localhost:3000/api/preview' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
noting these two urls work for local testing with next-build running separately outside of ddev.
these are overwritten in settings.tugboat.php
token_cron_batch_size: 0 | ||
public_key: ../public.key | ||
private_key: ../private.key |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
relative to docroot/
Description
Closes #15798. Closes #15791. Closes #15795. Closes #15792.
This is the CMS-half of the work for the above tickets, the next-build specific work was done in: department-of-veterans-affairs/next-build#227. Certain values have been stored in AWS SSM & are made available through env vars set in the Tugboat UI settings.
With all of that in place, this PR can now be tested on CMS Tugboats.
Testing done
I tested locally with this companion PR: department-of-veterans-affairs/next-build#227
Visit any story page (ex: https://pr15936-r38pi1elxdywfriwbyojfsw3jhrw8kwk.ci.cms.va.gov/wilmington-health-care/stories/wilmington-va-has-highest-drug-take-back-in-eastern-market) and see that the editor experience is unchanged. You can check other content types too, but it is not necessary.
To confirm all of the underlying wiring is in place correctly: enabled
Story
andStory Listing
as next site entities here: https://pr15936-r38pi1elxdywfriwbyojfsw3jhrw8kwk.ci.cms.va.gov/admin/config/services/next/entity-typesThis configuration was purposely not committed to prevent next-build being used for preview until it is ready. A follow-up PR will include these configs + feature flag handling around preview, along with the correct UI (preview link vs iframe takeover).
After the entities are enabled, visit the story page (ex: https://pr15936-r38pi1elxdywfriwbyojfsw3jhrw8kwk.ci.cms.va.gov/wilmington-health-care/stories/wilmington-va-has-highest-drug-take-back-in-eastern-market) and check the view tab. There should be an iframe instead of the standard editor experience. It may take a moment to render, and will likely appear broken until vets-website assets are in place. This is expected.
Now edit that story with some changes and save it as a draft. There should now be a
latest version
tab. Click that (https://pr15936-r38pi1elxdywfriwbyojfsw3jhrw8kwk.ci.cms.va.gov/node/63185/latest) and see that the iframe exists, rendering the updated draft content.Now create a new story with any data and save it unpublished. This content should also render in the iframe when looking at the
View
tab. (https://pr15936-r38pi1elxdywfriwbyojfsw3jhrw8kwk.ci.cms.va.gov/amarillo-health-care/stories/a-new-story)You will also see logs from the running next server in the tugboat dashboard here:
https://tugboat.vfs.va.gov/654196858b633cb05e2b7869
Screenshots
Unchanged:
AFTER NEXT JS ENTITY IS ENABLED
Published:
Draft revision:
Draft never published:
QA steps
What needs to be checked to prove this works?
What needs to be checked to prove it didn't break any related things?
What variations of circumstances (users, actions, values) need to be checked?
Definition of Done
Select Team for PR review
CMS Team
Public websites
Facilities
User support
Accelerated Publishing