Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Time / Location

  • Zoom, 11:00 AM

Attendees

Goals

The Campus API Gateway team would like to talk with Elda for a bit about having the SSIS Team take over maintenance on the developer.ucsb.edu website.

The Campus API Gateway team knows that we've talked about this idea a little bit before, but we want to have a conversation before we make a hand off:

  • Applying of security and upstream updates

  • Does your team have the time for this?

  • Does your team want to take on the responsibility?

  • How we would handle future small display/functionality updates?

  • How we would handle future larger functionality updates?

Agenda

Topic

Notes

Initial Thoughts

Scope of Expectations

  • Applying of security and upstream updates

  • There is a hope for an upgrade to Drupal 9

Current State (w/ Known Issues)

  • Currently on Drupal Core 8.9.19 (not installed through Composer)

  • Does not use an external SSO login provider (that’s a future project)

    • It does integrate with Apigee’s Developer system (the login credentials are stored in Drupal and they are linked to “Developers” in Apigee)

  • Most modules do not use Composer

    • There are a few modules which are using composer

    • "apigee/apigee-client-php": "^2.0",
"drupal/admin_toolbar": "^3.0",
"drupal/apigee_edge": "^1.20",
"drupal/captcha": "^1.2",
"drupal/markdown": "^1.3",
"drupal/modules_weight": "^1.9",

  • There are two warning messages that appears during dbupdates

    • Module layout_builder has an entry in the system.schema key/value storage, but is not installed.

    • Module workflow_state has an entry in the system.schema key/value storage, but is not installed.

    • I (Steven) believes both of these modules were remove the servers without doing a Uninstall module from the web interface. And these message indicate that the database/configuration has some old values hanging out in it.

    • I (Steven) was able to use these commands on my local installation, but they did not fix the problem when they were run “successfully” on the servers.

      • drush php-eval "\Drupal::keyValue('system.schema')->delete('layout_builder');"

      • drush php-eval "\Drupal::keyValue('system.schema')->delete('workflow_state');"

    • There’s a lot of information in https://ucsb-atlas.atlassian.net/browse/CMPRCWA-139

Process Questions

  • How we would handle future small display/functionality updates?

  • How we would handle future larger functionality updates?

Future Features We Would Like To Pursue

  • Apigee Teams Feature

    • Would happen along with integrating with Campus SSO

Decision to Hand Off

Answering the questions:

  • Does your team have the time for this?

  • Does your team want to take on the responsibility?

  • No labels