Feature: CLI cache warmup after cache:flush / cache:clean (optional HTTP GET)

[Genaker]

Preconditions

Magento 2.4+ with Magento_Backend enabled.

Steps

1. Configure optional warmup URLs under Stores > Configuration > Advanced > Developer > CLI Cache Warmup (or leave empty to use storefront base URL).
2. Run bin/magento cache:flush --warmup or bin/magento cache:clean --warmup, or standalone bin/magento cache:warmup.

Expected

After flush/clean, CLI can optionally perform HTTP GET requests to warm full-page cache (FPC) without requiring a third-party module or preferences.

Actual (before change)

No core option; merchants rely on custom code or external tools to warm caches after cache:flush / cache:clean.

Suggested approach

Implement in Magento_Backend:

• --warmup / -w on cache:flush and cache:clean
• New cache:warmup command
• Admin configuration for URLs and HTTP timeout

[m2-assistant]

Hi @Genaker. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• 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.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 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.

[github-jira-sync-bot]

❌ Something went wrong. Cannot create Jira issue.