You're viewing Apigee Edge documentation.
View Apigee X documentation.
The Apigee modules for Drupal 9 are open source projects that enable a self-hosted developer portal option for Apigee customers. Customers are responsible for hosting and maintaining portals that leverage these modules. As the maintenance status of the Apigee modules for Drupal 9 is "Actively maintained", all bug reports, tasks, and feature requests are best submitted as issues in GitHub where they will be addressed by maintainers.
This document covers the Apigee client for PHP and the following Apigee Drupal 9 modules:
The Apigee modules follow the Drupal release naming conventions, indicating the stability of each release. For example, releases listed as alpha or beta are not considered ready for production use, but are available for testing and feedback for the project.
Stable or official releases are considered stable code suitable for production use. Any critical bug in the Apigee modules (not due to configuration or code changes) that might cause data inconsistency, broken functionality, security issues, performance issues, or production impact is covered by the standard support process for Apigee customers. Customers can report a critical bug in the Apigee modules through the Apigee support portal.
Other Bugs or Feedback
For other bugs, questions, or feedback, open an issue in the GitHub project (see project page links above). Similarly, if you have a feature or improvement to suggest, open an issue in the related GitHub project. Pull requests are welcomed and encouraged! Please follow the contribution guidelines for each project and open an issue documenting your intended improvement before you write code, in order to facilitate discussion. There may be unanticipated use cases that could impact other users of the project.
For any issue, it is important to add steps to reproduce the behavior with a minimal install of Drupal core. We cannot address issues that we cannot replicate. If the issue is not reproducible in our system, it could be due to configuration or code changes.
Infrastructure and Hosting
Google does not support the infrastructure or hosting of your Drupal site itself, such as:
- Server setup and installation
- Performance issues unrelated to the Apigee Edge API
- Investigation of server errors
- Security issues
- SMTP/email issues
- Code/database backups
If you do not have the resources to host and maintain a server and database yourself, consider using one of our recommended hosting providers. You can also engage with one of our preferred vendors to get expert help on designing or maintaining your own infrastructure. To learn more, contact your Apigee account representative.
Custom Development and Configuration
A Drupal site is a fully-customizable application and bugs may be created by unintended configurations or custom code changes to the system. We will address questions and offer guidance for any issues pertaining to the Apigee modules, but Google cannot support all possible custom development or deployments you might choose for your system. Custom code must be maintained and supported by your development team. Examples include:
- SEO optimizations
- Installation and validation of non-Apigee provided modules and themes to site
- Custom theme and module creation
If you do not have Drupal expertise in-house, consider contacting a Google representative to learn how an implementation partner might help.
Software and System Maintenance
The maintenance of your infrastructure and site is not covered by support. We strongly encourage all developers and site owners to follow best security practices and keep Drupal core code, as well as contributed modules and plugins, up-to-date. The Drupal Update module can notify administrators when security and regular updates impacting the site are released. See Keeping Track of Updates for more information. Site owners can also track security releases, incidents, and vulnerabilities pertaining to Drupal core and contributed projects on Drupal's official security advisories page. Subscribe via RSS or follow @drupalsecurity on Twitter.