[Issue] #29174 Add save_rewrites_history to categories via API

[m2-assistant]

This issue is automatically created based on existing pull request: #29205: #29174 Add save_rewrites_history to categories via API

---

Support save_rewrites_history to categories API

Preconditions (*)

1. Magento 2.4-develop

Description (*)

See #29174

Fixed Issues (if relevant)

1. Fixes Category API should support save_rewrites_history for consistency reasons #29174

Steps to reproduce (*)

1. Go to Catalog - Categories and create a new Subcategory
2. Open Swagger (http://magentositewname.domain/swagger)
3. Generate Admin token via integrationAdminTokenServiceV1 POST /V1/integration/admin/token request
4. Copy the generated token into api_key field and click **apply
   
5. Perform the catalogCategoryRepositoryV1 PUT /V1/categories/{id} request with the following Parameters:

• id 2 (id of the previously created category)
• body

{
    "category": {
    "id": 5,
    "parent_id": 2,
    "name": "new name",
    "is_active": true,
    "position": 0,
    "level": 0,
    "created_at": "string",
    "updated_at": "string",
    "path": "string",
    "include_in_menu": true,
    "extension_attributes": {},
    "custom_attributes": [
      {
        "attribute_code": "url_key",
        "value": "new name1"
      },{
        "attribute_code":"save_rewrites_history",
        "value":1
        }
      ]
     }
    }

6. Verify if the Response body is correct.
   Example:
   
7. Open database table url_rewrite

Actual result (*)

The old url_rewriew record has been removed, and only the new record existed

Expected result (*)

The previous record is not removed

See example in #29174

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds are green)

[magento-engcom-team]

✅ Confirmed by @engcom-Bravo
Thank you for verifying the issue. Based on the provided information internal tickets MC-38102 were created

Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[magento-engcom-team]

Hi @m2-assistant[bot]. Thank you for your report.
The issue has been fixed in #29205 by @amenk in 2.4-develop branch
Related commit(s):

• 5307bad69e56266eedf6fe80cd9d6da4c7ec0344
• 00176f5a3a0c6671556ff28b66f437ffb1970060
• 4c99f0d4dc714de6fc49e2b7d2b5f9a28a243ec1
• f0ba72a4ba585e0f53f7d4bbb9de35f1a2ed49e1
• 0f983b209a5df48040dd9aa744847b19ce091bd2
• 7f380b6bf878d7c3257ef9e92ff982851943418a
• 3361e72bd8c8cbed271ad7547c3e48dc1d334fb3
• 79c54aecb267aa5ce9dea5e6bb4e96e0dcc7f803
• 99da072f8cef3250be8c54f236306d6fbc51ae0f
• f61a27af1429effd65f3706663223e1e295d707c
• 25111f0dcd1ecf050112647930accd057b2d901a
• c7822ff08cd1e9ae844f5133f590e3eb677c8feb
• df69e820fac74bf257b7c6ce133ec402747a27ee
• 6fde4babdb7be4b72a8c1401232582d24efce545
• 9f81b49ed1cc3ccf4c9abd437657bcfdacc5a8ab
• 9583212943f2208922482e4f075b56727d905f23
• 1ad44825f3ae89a97f9ca4957b519bf41e7b8f5b

The fix will be available with the upcoming 2.4.2 release.