bernardodemarco commented on PR #10790:
URL: https://github.com/apache/cloudstack/pull/10790#issuecomment-2841720959

   @DaanHoogland, yes, it is possible. This change only encompass scenarios in 
which the `value` parameter is not included in the API request. For instance:
   
   ```bash
   (all-in-one) 🐱 > update configuration name='alert.email.addresses'
   ```
   
   Currently, the Management Server handles this situation by only returning 
the configuration details:
   
   ```bash
   (all-in-one) 🐱 > update configuration name='alert.email.addresses'
   {
     "configuration": {
       "category": "Alert",
       "component": "management-server",
       "description": "Comma separated list of email addresses which are going 
to receive alert emails.",
       "displaytext": "Alert email addresses",
       "group": "Management Server",
       "isdynamic": false,
       "name": "alert.email.addresses",
       "subgroup": "Alerts",
       "type": "CSV"
     }
   }
   ```
   
   When performing such API calls, the value of the configuration is not 
changed. To set its value to be empty, the operator needs to explicitly set the 
`value` parameter to an empty string:
   
   ```bash
   (all-in-one) 🐱 > update configuration name='alert.email.addresses' value=''
   {
     "configuration": {
       "category": "Alert",
       "component": "management-server",
       "description": "Comma separated list of email addresses which are going 
to receive alert emails.",
       "displaytext": "Alert email addresses",
       "group": "Management Server",
       "isdynamic": false,
       "name": "alert.email.addresses",
       "subgroup": "Alerts",
       "type": "CSV",
       "value": ""
     }
   }
   ```
   
   However, I've just realized that, through the UI, it is indeed a little bit 
awkward for the operator to clear a configuration value. It's required to clear 
the input field, add an empty space and submit the changes. I'll apply some UI 
adjustments to enhance UX there 


-- 
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