Overview
The API management platform consists of two main tools - a developer portal, and a gateway, both described below. The developer portal is currently a Drupal 7 site, provided by Apigee, and customized by the UCSB Apigee team. The Apigee functionality is tightly integrated into the Drupal 7 site, allowing user accounts, apps, and API requests to be visible in the Gateway, and vice-versa. Currently this site is hosted under the UCSB Pantheon account. With the Drupal 8 version Apigee took a different approach. They split the Apigee modules from the Apigee Drupal site, and made them available as a separate install for any Drupal site.
Developer Portal (https://developer.ucsb.edu/): used for API discovery and access/publishing requests. API users sign up for the developer portal, create an App, and request access to APIs for their app.
Gateway (https://login.apigee.com/login): used for API publishing, execution, and statistics.
Resources
The API Team has limited Drupal resources. We are looking for resources to help with this transition to Drupal 8 and implement the new setup that Apigee has provided with this version.
The team consists of volunteer members and any automation that can be achieved with the maintenance of the Drupal site will be helpful to the team.
API Team:
Diana Antova - SIS&T, team lead
Steven Maglio - SIS&T, team co-lead
Ian Lessing (Unlicensed) - Library, Drupal resource
Kevin Wu - ETS
christian.montecino (Unlicensed) - ETS
Vince Nievares - Academic Affairs IT
Reinard Dolleschel - Biological Sciences Administration IT
Notes
| Phase | Requirements | Notes |
|---|
| Phase 1 | - New site creation using the public affairs distribution
- Apigee modules installation
- Transfer current site content
- Setup and transfer workflow and rules
- Migrate user accounts
- Home page design
| - Phase 1 will include the migration of the site "as-is" from Drupal 7 to Drupal 8.
- We estimate the project to take about 160 hours
- The Apigee team has limited resources that will be available to assist, provide guidance, and testing for the migration.
|
| Phase 2 | - Site redesign to accommodate additional areas
- Automate the lookup to check for Apigee module updates
- Automate the application of Apigee module update
- Connect to campus SSO
- Implement Apigee Teams feature
| - There is a need for a web presence for the campus DevOps initiative. The developer portal was created initially as a generic developer resource site (developer.ucsb.edu). With the API platform being the main purpose of the site initially, it's design centers around this function. We are hoping we can redesign it to better fit the vision of serving the developer community in a wider capacity.
- In addition, in Phase 2 we want to implement some site improvements, such as SSO integration, the Apigee teams feature, better integration with the campus identity system, and automation of the Apigee Drupal module updates.
- The resources for some of these tasks will be different as they will require direct involvement from the Apigee team and other campus teams.
|
| Phase 3 | - Account cleanup automation
- Move all components to AWS (database, existing code)
- Develop account cleanup code
- As part of the AWS migration we can migrate the Heroku components for the chatbot
| - This task is not directly related to the Drupal migration and will require different resources.
|