@blueorangutan package

@davidjumani a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress.

Packaging result: ✔️centos ✔️debian ✔️archive.
QA: http://primate-qa.cloudstack.cloud:8080/client/pr/893 (JID-3755)

@ravening This will make the form require the user to enter the account as well as domain which is redundant as he's already navigated to the desired account. Instead, would it be better to exclude passing the projectid if the current route contains "account" over at https://github.com/apache/cloudstack-primate/blob/master/src/utils/request.js#L83 ?

@ravening This will make the form require the user to enter the account as well as domain which is redundant as he's already navigated to the desired account. Instead, would it be better to exclude passing the projectid if the current route contains "account" over at https://github.com/apache/cloudstack-primate/blob/master/src/utils/request.js#L83 ?

@davidjumani we don't need to enter anything here. If we are in project view then project id is passed else account/domain will be taken from backend code

If we pass both account and domain in project view then exception is thrown

@ravening The account will be taken for the current user but say an admin will have to pass the account and domain while adding a certificate for another account, after having navigated to that account

Ping @ravening any update on this?

@ravening @rhtyd @davidjumani
can we do like this ?
(1) in project view, ssl cert will be uploaded to project account, no matter what current account is.
otherwise there is no way to upload ssl cert to a project.
(2) in normal view, ssl cert will be uploaded to the current account on web page.