Power virtual server implementation#32
Conversation
|
/packit build |
| "list", help="List all PowerVS instances in IBM Cloud" | ||
| ) | ||
|
|
||
| return parser |
There was a problem hiding this comment.
It is true, that this adds many more parameters compared to the original non-powerful builders.
But to me, it seems that they are not new or different. It's just that for normal builders, we have them in a config file. I don't know where the config is on Fedora Copr but in case of Internal Copr, it is the deployment repository and roles/copr/backend/templates/ibm-cloud-config.j2
Can we unify the configuration and use either parameters or a config file for both types of builders or is there some reason why we can't/shouldn't?
There was a problem hiding this comment.
This is not about configuration or powerful builders. This is a Python CLI implementation for managing resources in Power Virtual Server, IBM Cloud - the power in the name is just a coincidence. The PowerVS cloud is basically a completely different cloud than VPC (so we can't use something from the VPC cloud config), even though both are under the IBM Cloud... It's like AWS and Azure but under the same website... I'll update the description of this PR/commits later once I have the functionality fully tested
There was a problem hiding this comment.
I don't know where the config is on Fedora Copr
we don't use power virtual server cloud in fedora copr
nikromen
force-pushed
the
powervs
branch
10 times, most recently
from
e06f8f5 to
8219903
Compare
nikromen
force-pushed
the
powervs
branch
9 times, most recently
from
7b87d9e to
c89adcd
Compare
nikromen
force-pushed
the
powervs
branch
3 times, most recently
from
4347efc to
0b69aa2
Compare
3 participants
No description provided.