sureshanaparti opened a new pull request, #13264:
URL: https://github.com/apache/cloudstack/pull/13264

   ### Description
   
   This PR removed the duplicate configkey json.content.type. Preserved the 
same description for the config as now in the CloudStack deployment.
   
   The config key was added twice here: 
https://github.com/apache/cloudstack/pull/2848/files#diff-d4f381fc49d5bb07c76daf73677484cace911ff56eb08e60b253b6ef0273124d
 (in 4.12.0.0) and one config key is unused.
   
   
   ```
   mysql> SELECT * FROM cloud.configuration WHERE name = 'json.content.type'\G;
   *************************** 1. row ***************************
        category: Advanced
        instance: DEFAULT
       component: ApiServer
            name: json.content.type
           value: application/json; charset=UTF-8
     description: Http response content type for JSON
   default_value: application/json; charset=UTF-8
         updated: 2026-05-06 15:55:35
      is_dynamic: 0
        group_id: 1
     subgroup_id: 1
          parent: NULL
    display_text: Json content type
            kind: NULL
         options: NULL
           scope: 1
   1 row in set (0.01 sec)
   
   mysql> SELECT * FROM cloud.configuration WHERE description LIKE '%Http 
response content%'\G;
   *************************** 1. row ***************************
        category: Advanced
        instance: DEFAULT
       component: ApiServer
            name: json.content.type
           value: application/json; charset=UTF-8
     description: Http response content type for JSON
   default_value: application/json; charset=UTF-8
         updated: 2026-05-06 15:55:35
      is_dynamic: 0
        group_id: 1
     subgroup_id: 1
          parent: NULL
    display_text: Json content type
            kind: NULL
         options: NULL
           scope: 1
   1 row in set (0.01 sec)
   ```
   
   <!--- Describe your changes in DETAIL - And how has behaviour functionally 
changed. -->
   
   <!-- For new features, provide link to FS, dev ML discussion etc. -->
   <!-- In case of bug fix, the expected and actual behaviours, steps to 
reproduce. -->
   
   <!-- When "Fixes: #<id>" is specified, the issue/PR will automatically be 
closed when this PR gets merged -->
   <!-- For addressing multiple issues/PRs, use multiple "Fixes: #<id>" -->
   <!-- Fixes: # -->
   
   <!--- 
******************************************************************************* 
-->
   <!--- NOTE: AUTOMATION USES THE DESCRIPTIONS TO SET LABELS AND PRODUCE 
DOCUMENTATION. -->
   <!--- PLEASE PUT AN 'X' in only **ONE** box -->
   <!--- 
******************************************************************************* 
-->
   
   ### Types of changes
   
   - [ ] Breaking change (fix or feature that would cause existing 
functionality to change)
   - [ ] New feature (non-breaking change which adds functionality)
   - [ ] Bug fix (non-breaking change which fixes an issue)
   - [ ] Enhancement (improves an existing feature and functionality)
   - [x] Cleanup (Code refactoring and cleanup, that may add test cases)
   - [ ] Build/CI
   - [ ] Test (unit or integration test code)
   
   ### Feature/Enhancement Scale or Bug Severity
   
   #### Feature/Enhancement Scale
   
   - [ ] Major
   - [ ] Minor
   
   #### Bug Severity
   
   - [ ] BLOCKER
   - [ ] Critical
   - [ ] Major
   - [ ] Minor
   - [ ] Trivial
   
   ### Screenshots (if appropriate):
   
   ### How Has This Been Tested?
   
   <!-- Please describe in detail how you tested your changes. -->
   <!-- Include details of your testing environment, and the tests you ran to 
-->
   
   #### How did you try to break this feature and the system with this change?
   
   <!-- see how your change affects other areas of the code, etc. -->
   
   <!-- Please read the 
[CONTRIBUTING](https://github.com/apache/cloudstack/blob/main/CONTRIBUTING.md) 
document -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to