Compute v2: Flavor Access Add#687
Conversation
|
I forgot I had this ready to go. Rebased and cleaned up. Ready for review. |
|
Build failed.
|
|
Ah, OpenLab was helpful here: The test passes for me in Ocata. I wonder if Pike now validates the tenant ID. |
|
Build succeeded.
|
|
Yep. Hey, look at that. CI in action 😄 |
| flavorID := "e91758d6-a54a-4778-ad72-0c73a1cb695b" | ||
|
|
||
| accessOpts := flavors.AddAccessOpts{ | ||
| Tenant: "15153a0979884b59b0592248ef947921", |
There was a problem hiding this comment.
Since this is the documentation, shouldn't this be an UUID to provide the additional visual prompt as to an appropriate value? I know in the AddAccessOpts definition it states project/tenant ID, but I think it would be helpful to change here. It's an easy change, but not necessarily enough to hold up the patch on.
There was a problem hiding this comment.
The rest of the patch looks great.
There was a problem hiding this comment.
At least on Ocata, the project and user IDs are these kinds of strings rather than UUIDs:
Successfully created project ACPTTESTWZC1JOxR with ID 8befa1ba8c224584bb2b7b55c6e35a24
Has this changed post-Ocata?
There was a problem hiding this comment.
no, you're right. sorry for the noise.
There was a problem hiding this comment.
It's no problem at all.
| flavorID := "e91758d6-a54a-4778-ad72-0c73a1cb695b" | ||
|
|
||
| accessOpts := flavors.AddAccessOpts{ | ||
| Tenant: "15153a0979884b59b0592248ef947921", |
There was a problem hiding this comment.
no, you're right. sorry for the noise.
| // AddAccessOptsBuilder allows extensions to add additional parameters to the | ||
| // AddAccess requests. | ||
| type AddAccessOptsBuilder interface { | ||
| ToAddAccessMap() (map[string]interface{}, error) |
For #506
Code and reference is listed in #506