Merge lp:~jtv/juju-core/session-certificate into lp:~go-bot/juju-core/trunk
Status: | Merged |
---|---|
Approved by: | Jeroen T. Vermeulen |
Approved revision: | no longer in the source branch. |
Merged at revision: | 1315 |
Proposed branch: | lp:~jtv/juju-core/session-certificate |
Merge into: | lp:~go-bot/juju-core/trunk |
Prerequisite: | lp:~jtv/juju-core/create-gwacl-sessions |
Diff against target: |
113 lines (+67/-15) 2 files modified
environs/azure/environ.go (+45/-8) environs/azure/environ_test.go (+22/-7) |
To merge this branch: | bzr merge lp:~jtv/juju-core/session-certificate |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Jeroen T. Vermeulen (community) | Approve | ||
Review via email: mp+170611@code.launchpad.net |
Commit message
Create temporary cert file for each ManagementAPI.
For now, each high-level function in the Azure provider will create its own storage contexts and management-API objects as needed. In the case of the management API, that comes with a temporary file containing an Azure certificate. (There is another way to pass the certificate to go-curl, but we want to avoid the complications and especially the unknowns at this point).
Once done with your request(s) to the management, you release it. This cleans up the certificate file, but in the future it may also serve as a hook for connection pooling. We'll treat optimization as a separate problem — it seems easy but this sort of thing often brings out creative tendencies that aren't worth the time just at the moment. As long as we don't need any actual cleanup code for the storage-API side, we chose not to create a cleanup method there. This is all internal detail after all; it doesn't affect any exported APIs.
Seems rietveld is still confused about the branch target here, looks
like it's comparing against an older trunk?
From the diff in launchpad though, LGTM. Double check the merge makes
sense before landing. :)
https:/ /codereview. appspot. com/10443043/