Drupal 8 Project Requirements

Background & Business Value

We would like to upgrade our Drupal 7.X portal to Drupal 8.6+. This should allow for the platform to be on the latest, most supported, and most secure Drupal platform possible. Key improvements in Drupal 8.X that we hope to use are REST API Management endpoints, UCSB campus website branding, and the larger module repository available to 8.X.

The Drupal Core Team believes that Drupal 8.6 will be the first version to have a clear migration path from 7 to 8:

While the migration path is rapidly approaching stability, upgrading from Drupal 7 to Drupal 8 is not yet fully supported. The earliest we'll have an officially supported stable migration path from Drupal 7 to Drupal 8  will be in Drupal 8.6.0 in the second half of 2018, with some contributed modules following after that.

Apigee has been redeveloping their Drupal integration into a Drupal 8 Module, apigee-edge-drupal, which breaks from their previous Drupal 7 integration; where it was baked into the platform. Because of this new approach Apigee has been aligning their delivery of the new module to coincide with the release of Drupal 8.6 and the stable upgrade path.

Update: Drupal 8.6 has been released. They have published new guidance documents:

• Drupal 8.6.0 Release Notes (Notes about fully supported upgrade path)
• Preparing a site for Upgrading to Drupal 8
• Upgrading from Drupal 6 or 7 to Drupal 8
• Upgrading Drupal issue tracker (support tickets) from Drupal.org

Goals

• Upgrade to Drupal 8.6
• Keep all data in place (not have to copy/paste content of workflows)

Sub Goals

• Teams Feature
• SSO Integration

Assumptions

• Pantheon will be able to duplicate our current version of 7 into a sandbox for 8.
• Once we have the Sandbox working, we can get Apigee to officially take over/support the payments and support on the Drupal 8 instance.
  • Steven Maglio has started a support ticket with Apigee about the details of this (Apigee Support Case 1450540).

Out of Scope

Requirements

User Interaction, Design & Architecture

Upgrade Path 2019-04-11

• Denise will create a new instance of Drupal 8 using the Public Affairs custom upstream in Pantheon
• Denise will the setup the instance to use Composer, break the upstream source, and redesign the site to use UCSB standards but keep the feel of the current site.
• Denise and the API Team will then integrate the Apigee Drupal module and get it working.
  • Denise and the API Team will check if the Company/Teams feature will work
  • Denise and the API Team will check if CAS/SSO is possible
• The API Team will then transfer of the information from the old site to the new site (by hand).

Initial Thoughts on the Upgrade Path (Late 2018)

1. Create a Drupal 8.6 instance in a UCSB Pantheon Sandbox; using our upstream provider for the Theme.
2. Follow Drupal guidance on Preparing a Drupal 7 site for a Drupal 8 Upgrade
3. Follow Drupal guidance on Upgrading Drupal 6/7 to Drupal 8.
4. We would then add the apigee-edge-drupal module (https://www.drupal.org/project/apigee_edge) 
   1. We would also need https://github.com/apigee/edge-php-sdk module because it contains all the object that the apigee_edge module uses.
5. Make the Drupal 8 sandbox the new official site, by ...
   1. Switchover the DNS names for *developer.ucsb.edu 

Examples and References

• Apigee Edge Drupal 8.X Module (github)
  • Documentation
• Apigee Licensing During Upgrade with Pantheon Support Ticket (Case 1450543)
• Drupal Upgrade to 8.6 "stable and supported"
  • Drupal 9 Upgrade
  • Easy Drupal Upgrades Forever
• Apigee's Response to a Drupal 8 Upgrade Question (2016/10/19)

Some Notes from Meeting with Alex White from Apigee

See also: 2018-09-10 - Drupal 8 Meeting with Apigee

• End of October 2018 for Beta, but might go to General Availability in January 2019
• Once Drupal 7 support ending is announced, it will be about a year long process that support will be provided
• They will be focusing on the internal portal, and looking for the Drupal support to moved to partners and contributors
• What happens to the licensing if we move to Drupal 8
  • Apigee will no longer pay for Pantheon
  • Support issues for Drupal 8 will need to go through Pantheon
  • Support issues with the Drupal 8 Apigee module will now become github issue and supported by the community (but not official support with Apigee)
• Partner companies experienced with Drupal: Pantheon, Chapter 3, Achieve

Questions

Below is a list of questions to be addressed as a result of this requirements document: