Add optionnal parameter to cache:clean and cache:flush to exclude type(s)

[Nuranto]

Description (*)

In some occasions (deployment of a new version for instance), we may want to purge all cache except Full page cache. This forces us to run cache:clean or cache:flush with the list of all types except full_page. Would be nicer to be able to exclude a type in those commands.

Benefits

Simpler syntax, no need to change deployment code when a new type of cache is added by some extension.

Example

At the moment we use : ./magento cache:flush config layout block_html collections reflection db_ddl compiled_config eav customer_notification config_integration config_integration_api config_webservice translate adyen fishpig_wordpress

This feature request would allow to use : ./magento cache:flush --exclude full_page

[m2-assistant[bot]]

Hi @Nuranto. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, review the Magento Contributor Assistant documentation.

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

To learn more about issue processing workflow, refer to the Code Contributions.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

:warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[magento-deployment-service[bot]]

Hi @madbounce. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @madbounce, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[magento-deployment-service[bot]]

Hi @madbounce. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @madbounce, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[magento-deployment-service[bot]]

Hi @madbounce. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @madbounce, here is your Magento Instance: https://567e3bfb1f4fccb491c6ce5f7b59164e.instances.magento-community.engineering Admin access: https://567e3bfb1f4fccb491c6ce5f7b59164e.instances.magento-community.engineering/admin_e24e Login: dc6970e1 Password: b375765ce179

[magento-deployment-service[bot]]

Hi @madbounce. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @madbounce, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[magento-deployment-service[bot]]

Hi @madbounce. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @madbounce, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[magento-deployment-service[bot]]

Hi @madbounce. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @madbounce, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[magento-deployment-service[bot]]

Hi @madbounce. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @madbounce, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[magento-deployment-service[bot]]

Hi @madbounce. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @madbounce, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[madbounce]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @madbounce. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @madbounce, here is your Magento Instance: https://8697396f25ed9db29a319403d6b81d5a.instances.magento-community.engineering Admin access: https://8697396f25ed9db29a319403d6b81d5a.instances.magento-community.engineering/admin_0aae Login: e97b7924 Password: c17649653775

[sandy6666]

@magento I am working on this

[hostep]

Just FYI, but we found out today that even if you explicitly do not mention full_page as type, it will still flush FPC, I'm trying to fix this in: https://github.com/magento/magento2/pull/38215