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

   ### Description
   
   CloudStack has the functionality to upload volumes, templates, and local 
ISOs. To execute the process, ACS generates a link to the secondary storage 
(using its public IPs), where the resource must be sent. The *links* are always 
generated with the HTTPS protocol and the environment has to be configured to 
handle HTTPS, requiring us to have SSL certificates. However, for environments 
that do not need to use certificates (such as staging ones), via the UI, we 
need a workaround (get the URL generated by the API for generating upload 
links, open it in a new tab, and accept an insecure connection with the 
application).  
   
   The ACS was changed so that it also handles HTTP to upload 
volumes/images/ISOs according to the global configuration 
`use.https.to.upload`; then operators can choose whether to use the HTTPS or 
HTTP protocol to generate upload links. By default (true) HTTPS will be used.
   
   ### 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)
   - [x] Enhancement (improves an existing feature and functionality)
   - [ ] Cleanup (Code refactoring and cleanup, that may add test cases)
   
   #### Feature/Enhancement Scale
   
   - [ ] Major
   - [x] Minor
   
   ### How Has This Been Tested?
   In order to test the behavior, the value of the `use.https.to.upload` 
configuration was changed to `FALSE` and then checked if the upload of ISOs, 
volumes, and templates was carried out using the HTTP protocol.
   


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