vendor: update terraform-provider-ironic to v0.1.2 #84
Conversation
stbenjam
force-pushed
the
terraform
branch
3 times, most recently
from
6d6e673 to
aff56c5
Compare
|
Build SUCCESS, see build http://10.8.144.11:8080/job/dev-tools/649/ |
|
CI results aren't actually valid until openshift-metal3/dev-scripts#558 makes it in |
|
Build FAILURE, see build http://10.8.144.11:8080/job/dev-tools/663/ |
|
Build SUCCESS, see build http://10.8.144.11:8080/job/dev-tools/666/ |
|
This should be ready to go, it can go in now as the provider works with 0.11 or 0.12. This change enables inspection and cleaning on masters as well. |
|
Build FAILURE, see build http://10.8.144.11:8080/job/dev-tools/677/ |
stbenjam
changed the title
|
Build SUCCESS, see build http://10.8.144.11:8080/job/dev-tools/678/ |
|
lgtm, but I'd update the commit message to discuss the update to gophercloud and terraform-provider-openstack as well |
|
Updated the commit message |
|
Build SUCCESS, see build http://10.8.144.11:8080/job/dev-tools/681/ |
This updates terraform-provider-ironic to the latest version, which supports terraform 0.12. We'll need this for the next rebase. This release of the ironic provider also enables inspection and cleaning explicitly on the masters, and it sets instance_uuid correctly in Ironic. Due to gophercloud being updated, terraform-provider-openstack is being updated to 1.19 as well, as there were changes in gophercloud that break the older version of the provider.
|
terraform-provider-openstack 1.19.0 was released, so I've updated this to vendor that instead of pointing to |
|
Build SUCCESS, see build http://10.8.144.11:8080/job/dev-tools/688/ |
|
Could someone have a look at this? I'd like to start on the 4.2 rebase, but I can't until this is in. |
|
Thanks! |
This updates terraform-provider-ironic to the latest version, which
supports terraform 0.12. We'll need this for the next rebase. This
release of the ironic provider also enables inspection and cleaning
explicitly on the masters, and it sets instance_uuid correctly in
Ironic.
Due to gophercloud being updated, terraform-provider-openstack is being
updated to 1.19.0 which supports that version of gophercloud.
When we rebase to 4.2, the only step to upgrade to 0.12 should be running
terraform 0.12upgradein thedata/data/baremetaldirectory.