Closed (fixed)
Project:
Cloud
Version:
3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
16 Dec 2020 at 01:02 UTC
Updated:
31 Dec 2020 at 01:19 UTC
Jump to comment: Most recent, Most recent file
Fix the owner ID in AWS Cloud Key Pair
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | 3188595-12.diff | 12.5 KB | yas |
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
xiaohua guan commentedComment #4
yasComment #5
yas@xiaohua-guan
Thank you for fixing the issue. I posted my comment above. Could you please check it?
Comment #6
xiaohua guan commented@yas
I can't update the tag of a keypair after it is created. So I disabled the owner textfield.
Comment #7
yas@xiaohua-guan
It looks we can update a tag value from AWS Management Console. Can we update a tag value by using a sequence of deleteTags() and createTags() API in
KeyPairEditFrom::save()?Comment #8
xiaohua guan commented@yas
Thanks for your comment. I changed the code in order to modify owner id. Please take a look again.
FYI, in the last comment I said that I can't update tag because I failed to update tags of a key pair by using key pair name. I wanted to use the resource id of a key pair, but there was no such field, so I used key pair name.
After I confirmed APIs again, I found key pair ID, which is what I want. So I added the field and the problem was resolved.
Comment #9
yas@xiaohua-guan
Thank you for the update. I tested the patch
and it looks good to me. I'll merge the patch to3.xand close this issue asFixed.Comment #10
yas@xiaohua-guan
I tested the patch further more and it has an issue with the following error:
Here is the use case.
In this case, it looks the key pair entity doesn't have Key Pair ID. When I click Refresh button, it starts working. Therefore, I think we need to update the key pair information when
Savebutton to populate the Key Pair ID _OR_Editbutton to fill out the Key Pair IDCould you please address that?
Thanks
PS
Thank for the detailed explanation.
Comment #11
xiaohua guan commented@yas
Sorry for the bug. I fixed it and failed test cases. Please check again. Thanks.
Comment #12
yasComment #13
yas@xiaohua-guan
Thank you for the update. I tested the patch and it looks perfect now. I'll merge the patch to
3.xand close this issue asFixed.Comment #15
yas