magento / devdocs

[Deprecated] Magento Developer Documentation
Open Software License 3.0
674 stars 1.76k forks source link

Clarify requirements for upgrading services in Staging and Production #9529

Closed ak77-prime closed 1 year ago

ak77-prime commented 2 years ago

Is there an existing issue for this?

Which topic?

https://devdocs.magento.com/cloud/project/services.html

What's wrong with the content?

The bold text implies that we would be upgrading PHP for the merchant when that's not the case:

" For Pro projects, you must create a Support ticket to install or update services in Staging and Production environments. Indicate the service changes needed and include your updated .magento.app.yaml and services.yaml files and PHP version in the ticket. It can take up to 48 hours for the Cloud infrastructure team to update your project. "

PHP is not considered a service - the customer has to upgrade PHP themselves. The only reason why we would ask for the PHP version is to make sure that the following are upgraded to be compatible with the PHP version:

The only caveat is that the customer's project might not currently support PHP 8.1 - this requires an OS upgrade by Infrastructure.

I would also recommend updating the path to the services.yaml file

What changes do you propose?

For Pro projects, you must create a Support ticket to install or update services in Staging and Production environments. Indicate the service changes needed and include your updated .magento/services.yaml file - as well as the .magento.app.yaml file indicating the PHP version that you will be upgrading to and any any of these additional PHP extensions you might require.

It can take up to 48 hours for the Cloud infrastructure team to update your project.

Anything else that can help to cover this?

How to upgrade PHP

Extension support:

For Pro projects, the following extensions require additional support to install:

ioncube sourceguardian

Submit a support ticket to install these PHP extensions.

m2-assistant[bot] commented 2 years ago

Hi @ak77-prime. Thank you for your report. To speed up processing of this issue, make sure that you provided sufficient information.

Add a comment to assign the issue: @magento I am working on this