Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify the process of updating PHP version #442

Merged
merged 1 commit into from
Feb 20, 2023

Conversation

shadyvb
Copy link
Contributor

@shadyvb shadyvb commented Nov 28, 2022

Switch the steps so the PHP update request is done before the updated application code is deployed.

Switch the steps so the PHP update request is done before the updated application code is deployed.
@roborourke
Copy link
Contributor

I think we’ll need to update the playbook in-line with this suggestion as well if we haven’t already

Copy link
Contributor

@mikelittle mikelittle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me

@shadyvb
Copy link
Contributor Author

shadyvb commented Nov 29, 2022

@rob I'm not sure what playbook page talks about that, maybe you mean on Altis side ? if so, there is nothing there to change as the update is how/when the client requests the upgrade. If on client's side, I'm not aware of any playbook page, I'd always be consulting Altis docs.

@mikelittle mikelittle merged commit c103fb8 into master Feb 20, 2023
@mikelittle mikelittle deleted the clarify-php-update-coordination branch February 20, 2023 10:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants