[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-08-18 UTC。"],[[["\u003cp\u003eThis document provides information on the open-source Apigee modules for Drupal 10, which allow for a self-hosted developer portal for Apigee and Apigee hybrid users.\u003c/p\u003e\n"],["\u003cp\u003eThe Apigee modules for Drupal 10 are actively maintained, and issues or feedback should be submitted as GitHub issues for the maintainers to address.\u003c/p\u003e\n"],["\u003cp\u003eCritical bugs in the Apigee modules that cause significant issues are supported through the standard Apigee and Apigee hybrid support process, while other issues should be raised on GitHub.\u003c/p\u003e\n"],["\u003cp\u003eGoogle does not provide support for the hosting, infrastructure, or custom development aspects of the Drupal site itself, such as server setup, security issues, or custom themes and modules.\u003c/p\u003e\n"],["\u003cp\u003eUsers are responsible for the maintenance of their Drupal sites, including following security best practices and keeping Drupal core, modules, and plugins up-to-date.\u003c/p\u003e\n"]]],[],null,["# Support process for Apigee Drupal 10 modules\n\n*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\n\nThe Apigee modules for Drupal 10 are open source projects that enable a self-hosted developer portal option\nfor Apigee and Apigee hybrid customers. Customers are responsible for hosting and maintaining portals that leverage\nthese modules. As the maintenance status of the Apigee modules for Drupal 10 is\n[\"Actively maintained\"](https://www.drupal.org/node/1066982), all bug reports, tasks, and feature\nrequests are best submitted as issues in GitHub where they will be addressed by maintainers.\n\n\nThis document covers the [Apigee client for PHP](https://github.com/apigee/apigee-client-php)\nand the following Apigee Drupal 10 modules:\n\n- [Apigee](https://www.drupal.org/project/apigee_edge)\n- [Apigee Monetization](https://www.drupal.org/project/apigee_m10n)\n- [Apigee Developer Portal Kickstart](https://www.drupal.org/project/apigee_devportal_kickstart)\n- [Apigee API Catalog](https://www.drupal.org/project/apigee_api_catalog)\n\nVersion Conventions\n-------------------\n\nThe Apigee modules follow the [Drupal release naming\nconventions](https://www.drupal.org/node/1015226), indicating the stability of each release. For example, releases listed as **alpha**\nor **beta** are not considered ready for production use, but are available for testing and feedback\nfor the project.\n\nCritical Bugs\n-------------\n\n\nStable or official releases are considered stable code suitable for production use. Any critical bug\nin the Apigee modules (not due to configuration or code changes) that might cause data inconsistency,\nbroken functionality, security issues, performance issues, or production impact is covered by the standard support process\nfor Apigee and Apigee hybrid customers. Customers can report a critical bug in the Apigee modules through the\n[Apigee support portal](https://cloud.google.com/apigee/support/).\n\nOther Bugs or Feedback\n----------------------\n\n\nFor other bugs, questions, or feedback, open an issue in the GitHub project (see project page links above).\nSimilarly, if you have a feature or improvement to suggest, open an issue in the related GitHub project.\nPull requests are welcomed and encouraged! Please follow the contribution guidelines for each project\nand open an issue documenting your intended improvement before you write code, in order to facilitate\ndiscussion. There may be unanticipated use cases that could impact other users of the project.\n\n\nFor any issue, it is important to add steps to reproduce the behavior with a minimal install of Drupal core.\nWe cannot address issues that we cannot replicate. If the issue is not reproducible in our system,\nit could be due to configuration or code changes.\n\nInfrastructure and Hosting\n--------------------------\n\n\nGoogle does not support the infrastructure or hosting of your Drupal site itself, such as:\n\n- Server setup and installation\n- Performance issues unrelated to the Apigee API\n- Investigation of server errors\n- Security issues\n- SMTP/email issues\n- Code/database backups\n\n\nIf you do not have the resources to host and maintain a server and database yourself,\nconsider using one of our recommended hosting providers. You can also engage with one of our preferred\nvendors to get expert help on designing or maintaining your own infrastructure. To learn more,\ncontact your Apigee account representative.\n\nCustom Development and Configuration\n------------------------------------\n\n\nA Drupal site is a fully-customizable application and bugs may be created by unintended configurations\nor 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:\n\n- SEO optimizations\n- Installation and validation of non-Apigee provided modules and themes to site\n- Custom theme and module creation\n\n\nIf you do not have Drupal expertise in-house, consider contacting a Google representative to learn\nhow an implementation partner might help.\n\nSoftware and System Maintenance\n-------------------------------\n\n\nThe maintenance of your infrastructure and site is not covered by support.\nWe strongly encourage all developers and site owners to follow\n[best security practices](https://www.drupal.org/security/secure-configuration) and keep\nDrupal core code, as well as contributed modules and plugins, up-to-date. The Drupal Update module\ncan notify administrators when security and regular updates impacting the site are released. See\n[Keeping Track of Updates](https://www.drupal.org/docs/user_guide/en/security-announce.html) for more information.\nSite owners can also track security releases, incidents, and vulnerabilities pertaining to Drupal core\nand contributed projects on [Drupal's official security advisories page](https://www.drupal.org/security).\nSubscribe via RSS or follow [@drupalsecurity](https://twitter.com/drupalsecurity) on Twitter."]]
