openshift/installer
1
0
Fork 0
mirror of https://github.com/openshift/installer.git synced 2026-02-05 06:46:36 +01:00
Code Issues Releases Activity
Files
b246fd4baeeb16b256d7a1d2f2738827bad09d23
installer/go.mod

154 lines
9.9 KiB
Modula-2
Raw Normal View History

Add go.mod
2020-02-14 00:00:06 +01:00
module github.com/openshift/installer
bump the minimum version for building installer to go 1.14 With Go 1.14 the handling of modules has improved in the sense that all the subcommands `go {test, generate}` now use the vendor when available by default. This makes it easier for us to run generate using the vendored tools like controller-tools etc. as it now uses the checked in vendor.
2020-06-04 18:18:11 -07:00
go 1.14
Add go.mod
2020-02-14 00:00:06 +01:00
require (
*: Migrate to ignition config spec v3.1 The installer now generates spec v3.1 ignition config, instead of v2.2 (and v2.4 for openstack) as before. The v3.1 ignition config specification can be found at [1]. A detailed overview of the differences between specs v2 and v3 can be found at [2]. Notable differences are: - the `Filesystem` identifier on ignition file configs no longer exists - `Overwrite` now defaults to `false` (was `true` in spec v2), which is why it is now set explicitly to keep the same behaviour. - duplicate file configs are now prohibited, i.e. all contents and all appendices must be defined in a single config. - duplicate systemd unit configs are now prohibited, i.e. the content and all dropins must be defined in a single config. This commit: - Bumps ignition to v2.3.0 with support for config spec v3.1. - Bumps terraform-provider-ignition to v2.1.0. Also adds downloading of the provider binary to `images/installer/Dockerfile.upi.ci` which is necessary because the ignition v2/spec3 version from the `community-terraform-providers/terraform-ignition-provider` fork is not present in the provider registry that is maintained by Hashicorp and can therefore not be pulled in automatically by terraform. is not present in the - Bumps machine-config-operator to b3b074ee9156 (latest commit at the time of this writing). - Adds "github.com/clarketm/json" dependency for marshaling Ignition configs. This is a dropin replacement for "encoding/json" that supports zero values of structs with omittempty annotations when marshaling. In effect, this will exclude empty pointer struct fields from the marshaled data instead of inserting nil values into them, which do not pass openAPI validation on fields that are supposed to contain e.g. strings. The same library is used by machine-config-operator and ignition itself. - Updates the vendor dir to make commit idempotent. [1] https://github.com/coreos/ignition/blob/master/doc/configuration-v3_1.md [2] https://github.com/coreos/ignition/blob/master/doc/migrating-configs.md#from-version-230-to-300 Co-authored-by: Vadim Rutkovsky <vrutkovs@redhat.com>
2020-07-21 18:39:41 +02:00
cloud.google.com/go v0.57.0
vendor: bump terraform-provider-azure to version v2.17.0
2020-07-07 09:40:31 -07:00
github.com/Azure/azure-sdk-for-go v43.2.0+incompatible
Upgrade terraform-provider-azurerm to v2.8.0 from the openshift fork
2020-04-29 17:57:45 -03:00
github.com/Azure/go-autorest/autorest v0.10.0
github.com/Azure/go-autorest/autorest/adal v0.8.2
Add go.mod
2020-02-14 00:00:06 +01:00
github.com/Azure/go-autorest/autorest/azure/auth v0.4.1
github.com/Azure/go-autorest/autorest/to v0.3.1-0.20191028180845-3492b2aff503
github.com/Azure/go-ntlmssp v0.0.0-20191115210519-2b2be6cc8ed4 // indirect
github.com/ChrisTrenkamp/goxpath v0.0.0-20190607011252-c5096ec8773d // indirect
github.com/Netflix/go-expect v0.0.0-20190729225929-0e00d9168667 // indirect
github.com/antchfx/xpath v1.1.2 // indirect
github.com/apparentlymart/go-cidr v1.0.1
github.com/awalterschulze/gographviz v0.0.0-20190522210029-fa59802746ab
vendor: bump terraform-provider-aws to to version v2.67.0
2020-07-01 20:37:52 -07:00
github.com/aws/aws-sdk-go v1.32.3
Add go.mod
2020-02-14 00:00:06 +01:00
github.com/btubbs/datetime v0.1.1 // indirect
github.com/c4milo/gotoolkit v0.0.0-20190525173301-67483a18c17a // indirect
*: Migrate to ignition config spec v3.1 The installer now generates spec v3.1 ignition config, instead of v2.2 (and v2.4 for openstack) as before. The v3.1 ignition config specification can be found at [1]. A detailed overview of the differences between specs v2 and v3 can be found at [2]. Notable differences are: - the `Filesystem` identifier on ignition file configs no longer exists - `Overwrite` now defaults to `false` (was `true` in spec v2), which is why it is now set explicitly to keep the same behaviour. - duplicate file configs are now prohibited, i.e. all contents and all appendices must be defined in a single config. - duplicate systemd unit configs are now prohibited, i.e. the content and all dropins must be defined in a single config. This commit: - Bumps ignition to v2.3.0 with support for config spec v3.1. - Bumps terraform-provider-ignition to v2.1.0. Also adds downloading of the provider binary to `images/installer/Dockerfile.upi.ci` which is necessary because the ignition v2/spec3 version from the `community-terraform-providers/terraform-ignition-provider` fork is not present in the provider registry that is maintained by Hashicorp and can therefore not be pulled in automatically by terraform. is not present in the - Bumps machine-config-operator to b3b074ee9156 (latest commit at the time of this writing). - Adds "github.com/clarketm/json" dependency for marshaling Ignition configs. This is a dropin replacement for "encoding/json" that supports zero values of structs with omittempty annotations when marshaling. In effect, this will exclude empty pointer struct fields from the marshaled data instead of inserting nil values into them, which do not pass openAPI validation on fields that are supposed to contain e.g. strings. The same library is used by machine-config-operator and ignition itself. - Updates the vendor dir to make commit idempotent. [1] https://github.com/coreos/ignition/blob/master/doc/configuration-v3_1.md [2] https://github.com/coreos/ignition/blob/master/doc/migrating-configs.md#from-version-230-to-300 Co-authored-by: Vadim Rutkovsky <vrutkovs@redhat.com>
2020-07-21 18:39:41 +02:00
github.com/clarketm/json v1.14.1
Add go.mod
2020-02-14 00:00:06 +01:00
github.com/containers/image v3.0.2+incompatible
*: Migrate to ignition config spec v3.1 The installer now generates spec v3.1 ignition config, instead of v2.2 (and v2.4 for openstack) as before. The v3.1 ignition config specification can be found at [1]. A detailed overview of the differences between specs v2 and v3 can be found at [2]. Notable differences are: - the `Filesystem` identifier on ignition file configs no longer exists - `Overwrite` now defaults to `false` (was `true` in spec v2), which is why it is now set explicitly to keep the same behaviour. - duplicate file configs are now prohibited, i.e. all contents and all appendices must be defined in a single config. - duplicate systemd unit configs are now prohibited, i.e. the content and all dropins must be defined in a single config. This commit: - Bumps ignition to v2.3.0 with support for config spec v3.1. - Bumps terraform-provider-ignition to v2.1.0. Also adds downloading of the provider binary to `images/installer/Dockerfile.upi.ci` which is necessary because the ignition v2/spec3 version from the `community-terraform-providers/terraform-ignition-provider` fork is not present in the provider registry that is maintained by Hashicorp and can therefore not be pulled in automatically by terraform. is not present in the - Bumps machine-config-operator to b3b074ee9156 (latest commit at the time of this writing). - Adds "github.com/clarketm/json" dependency for marshaling Ignition configs. This is a dropin replacement for "encoding/json" that supports zero values of structs with omittempty annotations when marshaling. In effect, this will exclude empty pointer struct fields from the marshaled data instead of inserting nil values into them, which do not pass openAPI validation on fields that are supposed to contain e.g. strings. The same library is used by machine-config-operator and ignition itself. - Updates the vendor dir to make commit idempotent. [1] https://github.com/coreos/ignition/blob/master/doc/configuration-v3_1.md [2] https://github.com/coreos/ignition/blob/master/doc/migrating-configs.md#from-version-230-to-300 Co-authored-by: Vadim Rutkovsky <vrutkovs@redhat.com>
2020-07-21 18:39:41 +02:00
github.com/coreos/ignition/v2 v2.3.0
vendor: update terraform-provider-libvirt to 0.6.2 Version 0.6.2 includes a fix for injecting ignition config required by both s390x and ppc64le architectures.
2020-05-02 08:46:48 +01:00
github.com/dmacvicar/terraform-provider-libvirt v0.6.2
Add go.mod
2020-02-14 00:00:06 +01:00
github.com/frankban/quicktest v1.7.2 // indirect
github.com/ghodss/yaml v1.0.1-0.20190212211648-25d852aebe32
vendor: Added go-playground/validator module This module simplify and make more scalable the validation steps, It's annotations based, offers a good set of pre-existing validation rules and allows to add easily new custom validation rules
2020-03-04 12:05:18 +01:00
github.com/go-playground/validator/v10 v10.2.0
vendor: bump gcp tf provider to v3.27.0
2020-06-26 19:21:04 -07:00
github.com/golang/mock v1.4.3
*: Migrate to ignition config spec v3.1 The installer now generates spec v3.1 ignition config, instead of v2.2 (and v2.4 for openstack) as before. The v3.1 ignition config specification can be found at [1]. A detailed overview of the differences between specs v2 and v3 can be found at [2]. Notable differences are: - the `Filesystem` identifier on ignition file configs no longer exists - `Overwrite` now defaults to `false` (was `true` in spec v2), which is why it is now set explicitly to keep the same behaviour. - duplicate file configs are now prohibited, i.e. all contents and all appendices must be defined in a single config. - duplicate systemd unit configs are now prohibited, i.e. the content and all dropins must be defined in a single config. This commit: - Bumps ignition to v2.3.0 with support for config spec v3.1. - Bumps terraform-provider-ignition to v2.1.0. Also adds downloading of the provider binary to `images/installer/Dockerfile.upi.ci` which is necessary because the ignition v2/spec3 version from the `community-terraform-providers/terraform-ignition-provider` fork is not present in the provider registry that is maintained by Hashicorp and can therefore not be pulled in automatically by terraform. is not present in the - Bumps machine-config-operator to b3b074ee9156 (latest commit at the time of this writing). - Adds "github.com/clarketm/json" dependency for marshaling Ignition configs. This is a dropin replacement for "encoding/json" that supports zero values of structs with omittempty annotations when marshaling. In effect, this will exclude empty pointer struct fields from the marshaled data instead of inserting nil values into them, which do not pass openAPI validation on fields that are supposed to contain e.g. strings. The same library is used by machine-config-operator and ignition itself. - Updates the vendor dir to make commit idempotent. [1] https://github.com/coreos/ignition/blob/master/doc/configuration-v3_1.md [2] https://github.com/coreos/ignition/blob/master/doc/migrating-configs.md#from-version-230-to-300 Co-authored-by: Vadim Rutkovsky <vrutkovs@redhat.com>
2020-07-21 18:39:41 +02:00
github.com/golang/protobuf v1.4.1
Add go.mod
2020-02-14 00:00:06 +01:00
github.com/google/martian v2.1.1-0.20190517191504-25dcb96d9e51+incompatible // indirect
github.com/google/uuid v1.1.1
openstack: Upgrade the Terraform provider
2020-09-25 14:12:37 +02:00
github.com/gophercloud/gophercloud v0.12.1-0.20200821143728-362eb785d617
Bump gophercloud to 0.11.0 Gophercloud 0.10.0 contains a breaking change, where all IDFromName functions were moved to a standalone gophercloud/utils repo: https://github.com/gophercloud/gophercloud/blob/master/CHANGELOG.md#0100-april-12-2020 This PR also addresses this change.
2020-06-22 12:56:30 +02:00
github.com/gophercloud/utils v0.0.0-20200508015959-b0167b94122c
cache: Support artifacts compressed with xz Switches to "github.com/h2non/filetype/matchers" for MIME type matching and uses "github.com/ulikunitz/xz" for xz decompression.
2020-02-27 22:56:18 +01:00
github.com/h2non/filetype v1.0.12
Add go.mod
2020-02-14 00:00:06 +01:00
github.com/hashicorp/go-azure-helpers v0.10.0
*: Migrate to ignition config spec v3.1 The installer now generates spec v3.1 ignition config, instead of v2.2 (and v2.4 for openstack) as before. The v3.1 ignition config specification can be found at [1]. A detailed overview of the differences between specs v2 and v3 can be found at [2]. Notable differences are: - the `Filesystem` identifier on ignition file configs no longer exists - `Overwrite` now defaults to `false` (was `true` in spec v2), which is why it is now set explicitly to keep the same behaviour. - duplicate file configs are now prohibited, i.e. all contents and all appendices must be defined in a single config. - duplicate systemd unit configs are now prohibited, i.e. the content and all dropins must be defined in a single config. This commit: - Bumps ignition to v2.3.0 with support for config spec v3.1. - Bumps terraform-provider-ignition to v2.1.0. Also adds downloading of the provider binary to `images/installer/Dockerfile.upi.ci` which is necessary because the ignition v2/spec3 version from the `community-terraform-providers/terraform-ignition-provider` fork is not present in the provider registry that is maintained by Hashicorp and can therefore not be pulled in automatically by terraform. is not present in the - Bumps machine-config-operator to b3b074ee9156 (latest commit at the time of this writing). - Adds "github.com/clarketm/json" dependency for marshaling Ignition configs. This is a dropin replacement for "encoding/json" that supports zero values of structs with omittempty annotations when marshaling. In effect, this will exclude empty pointer struct fields from the marshaled data instead of inserting nil values into them, which do not pass openAPI validation on fields that are supposed to contain e.g. strings. The same library is used by machine-config-operator and ignition itself. - Updates the vendor dir to make commit idempotent. [1] https://github.com/coreos/ignition/blob/master/doc/configuration-v3_1.md [2] https://github.com/coreos/ignition/blob/master/doc/migrating-configs.md#from-version-230-to-300 Co-authored-by: Vadim Rutkovsky <vrutkovs@redhat.com>
2020-07-21 18:39:41 +02:00
github.com/hashicorp/go-plugin v1.2.2
Add go.mod
2020-02-14 00:00:06 +01:00
github.com/hashicorp/logutils v1.0.0
go.mod: tf-provider-vsphere: Switch back from fork With v1.16.2 the provider has migrated to using the terraform-plugin-sdk, therefore the installer can now switch back from using a forked version.
2020-03-09 18:06:18 +01:00
github.com/hashicorp/terraform v0.12.21
openstack: Upgrade the Terraform provider
2020-09-25 14:12:37 +02:00
github.com/hashicorp/terraform-plugin-sdk v1.15.0
Add go.mod
2020-02-14 00:00:06 +01:00
github.com/hashicorp/vault v1.3.0 // indirect
github.com/hinshun/vt10x v0.0.0-20180809195222-d55458df857c // indirect
github.com/keybase/go-crypto v0.0.0-20190828182435-a05457805304 // indirect
github.com/libvirt/libvirt-go v5.10.0+incompatible
github.com/libvirt/libvirt-go-xml v5.10.0+incompatible // indirect
github.com/masterzen/simplexml v0.0.0-20190410153822-31eea3082786 // indirect
github.com/masterzen/winrm v0.0.0-20190308153735-1d17eaf15943 // indirect
github.com/metal3-io/baremetal-operator v0.0.0
github.com/metal3-io/cluster-api-provider-baremetal v0.0.0
*: Migrate to ignition config spec v3.1 The installer now generates spec v3.1 ignition config, instead of v2.2 (and v2.4 for openstack) as before. The v3.1 ignition config specification can be found at [1]. A detailed overview of the differences between specs v2 and v3 can be found at [2]. Notable differences are: - the `Filesystem` identifier on ignition file configs no longer exists - `Overwrite` now defaults to `false` (was `true` in spec v2), which is why it is now set explicitly to keep the same behaviour. - duplicate file configs are now prohibited, i.e. all contents and all appendices must be defined in a single config. - duplicate systemd unit configs are now prohibited, i.e. the content and all dropins must be defined in a single config. This commit: - Bumps ignition to v2.3.0 with support for config spec v3.1. - Bumps terraform-provider-ignition to v2.1.0. Also adds downloading of the provider binary to `images/installer/Dockerfile.upi.ci` which is necessary because the ignition v2/spec3 version from the `community-terraform-providers/terraform-ignition-provider` fork is not present in the provider registry that is maintained by Hashicorp and can therefore not be pulled in automatically by terraform. is not present in the - Bumps machine-config-operator to b3b074ee9156 (latest commit at the time of this writing). - Adds "github.com/clarketm/json" dependency for marshaling Ignition configs. This is a dropin replacement for "encoding/json" that supports zero values of structs with omittempty annotations when marshaling. In effect, this will exclude empty pointer struct fields from the marshaled data instead of inserting nil values into them, which do not pass openAPI validation on fields that are supposed to contain e.g. strings. The same library is used by machine-config-operator and ignition itself. - Updates the vendor dir to make commit idempotent. [1] https://github.com/coreos/ignition/blob/master/doc/configuration-v3_1.md [2] https://github.com/coreos/ignition/blob/master/doc/migrating-configs.md#from-version-230-to-300 Co-authored-by: Vadim Rutkovsky <vrutkovs@redhat.com>
2020-07-21 18:39:41 +02:00
github.com/mitchellh/cli v1.1.1
baremetal: Add diagnostic error message for ironic terraform errors This PR enables the installer to track certain ironic terraform provider error messages and translates it into easy-to-understand errors output by the installer. Examples: Terraform errors such as "Error: could not contact Ironic API: timeout reached" and "Error: could not inspect: could not inspect node, node is currently 'inspect failed', last error was 'timeout reached while inspecting the node" will each get translated to their corresponding user-friendly error messages.
2020-07-21 17:57:44 -05:00
github.com/openshift-metal3/terraform-provider-ironic v0.2.3
Add go.mod
2020-02-14 00:00:06 +01:00
github.com/openshift/api v3.9.1-0.20191111211345-a27ff30ebf09+incompatible
Revendor after updating MAO
2020-04-29 15:21:57 +02:00
github.com/openshift/client-go v0.0.0-20200320150128-a906f3d8e723
vendor update cloud-credential-operator ``` $ go version go version go1.14 linux/amd64 $ go mod edit -require github.com/openshift/cloud-credential-operator@master $ go mod tidy warning: ignoring symlink /home/adahiya/go/src/github.com/openshift/installer/pkg/asset/store/data go: downloading github.com/openshift/cloud-credential-operator v0.0.0-20200316201045-d10080b52c9e $ go mod vendor ``` brings in changes from https://github.com/openshift/cloud-credential-operator/pull/167
2020-03-15 11:32:39 -07:00
github.com/openshift/cloud-credential-operator v0.0.0-20200316201045-d10080b52c9e
Add go.mod
2020-02-14 00:00:06 +01:00
github.com/openshift/cluster-api v0.0.0-20191129101638-b09907ac6668
github.com/openshift/cluster-api-provider-gcp v0.0.1-0.20200120152131-1b09fd9e7156
github.com/openshift/cluster-api-provider-libvirt v0.2.1-0.20191219173431-2336783d4603
ovirt: bump terraform and cluster-api providers Signed-off-by: Roy Golan <rgolan@redhat.com>
2020-04-03 12:04:18 +03:00
github.com/openshift/cluster-api-provider-ovirt v0.1.1-0.20200504092944-27473ea1ae43
Revendor after updating MAO
2020-04-29 15:21:57 +02:00
github.com/openshift/library-go v0.0.0-20200324092245-db2a8546af81
github.com/openshift/machine-api-operator v0.2.1-0.20200429102619-d36974451290
*: Migrate to ignition config spec v3.1 The installer now generates spec v3.1 ignition config, instead of v2.2 (and v2.4 for openstack) as before. The v3.1 ignition config specification can be found at [1]. A detailed overview of the differences between specs v2 and v3 can be found at [2]. Notable differences are: - the `Filesystem` identifier on ignition file configs no longer exists - `Overwrite` now defaults to `false` (was `true` in spec v2), which is why it is now set explicitly to keep the same behaviour. - duplicate file configs are now prohibited, i.e. all contents and all appendices must be defined in a single config. - duplicate systemd unit configs are now prohibited, i.e. the content and all dropins must be defined in a single config. This commit: - Bumps ignition to v2.3.0 with support for config spec v3.1. - Bumps terraform-provider-ignition to v2.1.0. Also adds downloading of the provider binary to `images/installer/Dockerfile.upi.ci` which is necessary because the ignition v2/spec3 version from the `community-terraform-providers/terraform-ignition-provider` fork is not present in the provider registry that is maintained by Hashicorp and can therefore not be pulled in automatically by terraform. is not present in the - Bumps machine-config-operator to b3b074ee9156 (latest commit at the time of this writing). - Adds "github.com/clarketm/json" dependency for marshaling Ignition configs. This is a dropin replacement for "encoding/json" that supports zero values of structs with omittempty annotations when marshaling. In effect, this will exclude empty pointer struct fields from the marshaled data instead of inserting nil values into them, which do not pass openAPI validation on fields that are supposed to contain e.g. strings. The same library is used by machine-config-operator and ignition itself. - Updates the vendor dir to make commit idempotent. [1] https://github.com/coreos/ignition/blob/master/doc/configuration-v3_1.md [2] https://github.com/coreos/ignition/blob/master/doc/migrating-configs.md#from-version-230-to-300 Co-authored-by: Vadim Rutkovsky <vrutkovs@redhat.com>
2020-07-21 18:39:41 +02:00
github.com/openshift/machine-config-operator v0.0.0
Bump go-ovirt Solve an issue related to RHV work parsing Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=1838559 Signed-off-by: Roberto Ciatti <rciatti@redhat.com>
2020-06-30 18:48:58 +02:00
github.com/ovirt/go-ovirt v0.0.0-20200613023950-320a86f9df27
Bug 1874747: ovirt: dont start the temp VM before template creation - bump terraform provider with the required param - add param to the installer not to start the VM when creating template. Signed-off-by: Evgeny Slutsky <eslutsky@redhat.com>
2020-09-13 15:41:47 +03:00
github.com/ovirt/terraform-provider-ovirt v0.4.3-0.20200914080915-c4444fb5c201
Add go.mod
2020-02-14 00:00:06 +01:00
github.com/packer-community/winrmcp v0.0.0-20180921211025-c76d91c1e7db // indirect
github.com/pborman/uuid v1.2.0
github.com/pierrec/lz4 v2.3.0+incompatible // indirect
github.com/pkg/errors v0.9.1
github.com/pkg/sftp v1.10.1
vendor: Added prometheus dependencies Added the dependencies for prometheus in the vendor folder along with some indirect dependencies.
2020-07-13 14:45:47 -04:00
github.com/prometheus/client_golang v1.5.1
vendor: Add prometheus push client dependencies Added additional prometheus push client dependencies that are required to push.
2020-07-22 11:03:25 -04:00
github.com/prometheus/common v0.9.1
Add go.mod
2020-02-14 00:00:06 +01:00
github.com/satori/uuid v1.2.0 // indirect
github.com/shurcooL/vfsgen v0.0.0-20181202132449-6a9ea43bcacd
baremetal: vendor: bump baremetal-operator This updates baremetal-operator to pull in the latest changes including hardware profiles. The installer vendors hardware profiles from baremetal-operator to keep the interface the same between terraform-provisioned baremetal hosts and those provisioned by the machine-api. This is done by updating the entry in the `replace` clause of the go.mod file. Then, we run `go mod tidy`, followed by `go mod vendor`. This breaks because the requested version of google.golang.org/grpc, v1.27.0, changes the API in backwards-incompatible ways. Thus, we also include a new pin for this dependency to the previously requested version, v1.25.0, which yields a working build.
2020-06-16 11:12:52 -03:00
github.com/sirupsen/logrus v1.5.0
github.com/spf13/cobra v0.0.6
Add go.mod
2020-02-14 00:00:06 +01:00
github.com/stoewer/go-strcase v1.1.0 // indirect
vendor: use openshift fork of terraform-provider-aws and bump to v2.60.0 This is to address the "NoSuchBucket: The specified bucket does not exist" error as explained in https://bugzilla.redhat.com/show_bug.cgi?id=1759617 and many other similar bugs. This bug has been "fixed" several times over the years, yet it continues to rear its ugly self. The ultimate problem is a race condition with S3 eventual consistency. As described in the bug above, the bucket does not yet exist when trying to reference tags. The openshift fork that this commit references, contains an upstream patch as described in https://github.com/terraform-providers/terraform-provider-aws/pull/13009 that should address this issue.
2020-05-19 09:51:52 -07:00
github.com/stretchr/testify v1.5.1
openstack: Upgrade the Terraform provider
2020-09-25 14:12:37 +02:00
github.com/terraform-provider-openstack/terraform-provider-openstack v1.32.0
vendor: use openshift fork of terraform-provider-aws and bump to v2.60.0 This is to address the "NoSuchBucket: The specified bucket does not exist" error as explained in https://bugzilla.redhat.com/show_bug.cgi?id=1759617 and many other similar bugs. This bug has been "fixed" several times over the years, yet it continues to rear its ugly self. The ultimate problem is a race condition with S3 eventual consistency. As described in the bug above, the bucket does not yet exist when trying to reference tags. The openshift fork that this commit references, contains an upstream patch as described in https://github.com/terraform-providers/terraform-provider-aws/pull/13009 that should address this issue.
2020-05-19 09:51:52 -07:00
github.com/terraform-providers/terraform-provider-aws v0.0.0
Add go.mod
2020-02-14 00:00:06 +01:00
github.com/terraform-providers/terraform-provider-azurerm v0.0.0
vendor: bump gcp tf provider to v3.27.0
2020-06-26 19:21:04 -07:00
github.com/terraform-providers/terraform-provider-google v1.20.1-0.20200623174414-27107f2ee160
*: Migrate to ignition config spec v3.1 The installer now generates spec v3.1 ignition config, instead of v2.2 (and v2.4 for openstack) as before. The v3.1 ignition config specification can be found at [1]. A detailed overview of the differences between specs v2 and v3 can be found at [2]. Notable differences are: - the `Filesystem` identifier on ignition file configs no longer exists - `Overwrite` now defaults to `false` (was `true` in spec v2), which is why it is now set explicitly to keep the same behaviour. - duplicate file configs are now prohibited, i.e. all contents and all appendices must be defined in a single config. - duplicate systemd unit configs are now prohibited, i.e. the content and all dropins must be defined in a single config. This commit: - Bumps ignition to v2.3.0 with support for config spec v3.1. - Bumps terraform-provider-ignition to v2.1.0. Also adds downloading of the provider binary to `images/installer/Dockerfile.upi.ci` which is necessary because the ignition v2/spec3 version from the `community-terraform-providers/terraform-ignition-provider` fork is not present in the provider registry that is maintained by Hashicorp and can therefore not be pulled in automatically by terraform. is not present in the - Bumps machine-config-operator to b3b074ee9156 (latest commit at the time of this writing). - Adds "github.com/clarketm/json" dependency for marshaling Ignition configs. This is a dropin replacement for "encoding/json" that supports zero values of structs with omittempty annotations when marshaling. In effect, this will exclude empty pointer struct fields from the marshaled data instead of inserting nil values into them, which do not pass openAPI validation on fields that are supposed to contain e.g. strings. The same library is used by machine-config-operator and ignition itself. - Updates the vendor dir to make commit idempotent. [1] https://github.com/coreos/ignition/blob/master/doc/configuration-v3_1.md [2] https://github.com/coreos/ignition/blob/master/doc/migrating-configs.md#from-version-230-to-300 Co-authored-by: Vadim Rutkovsky <vrutkovs@redhat.com>
2020-07-21 18:39:41 +02:00
github.com/terraform-providers/terraform-provider-ignition/v2 v2.1.0
Add go.mod
2020-02-14 00:00:06 +01:00
github.com/terraform-providers/terraform-provider-local v1.4.0
github.com/terraform-providers/terraform-provider-random v1.3.2-0.20190925210718-83518d96ae4f
go.mod: tf-provider-vsphere: Switch back from fork With v1.16.2 the provider has migrated to using the terraform-plugin-sdk, therefore the installer can now switch back from using a forked version.
2020-03-09 18:06:18 +01:00
github.com/terraform-providers/terraform-provider-vsphere v1.16.2
*: Migrate to ignition config spec v3.1 The installer now generates spec v3.1 ignition config, instead of v2.2 (and v2.4 for openstack) as before. The v3.1 ignition config specification can be found at [1]. A detailed overview of the differences between specs v2 and v3 can be found at [2]. Notable differences are: - the `Filesystem` identifier on ignition file configs no longer exists - `Overwrite` now defaults to `false` (was `true` in spec v2), which is why it is now set explicitly to keep the same behaviour. - duplicate file configs are now prohibited, i.e. all contents and all appendices must be defined in a single config. - duplicate systemd unit configs are now prohibited, i.e. the content and all dropins must be defined in a single config. This commit: - Bumps ignition to v2.3.0 with support for config spec v3.1. - Bumps terraform-provider-ignition to v2.1.0. Also adds downloading of the provider binary to `images/installer/Dockerfile.upi.ci` which is necessary because the ignition v2/spec3 version from the `community-terraform-providers/terraform-ignition-provider` fork is not present in the provider registry that is maintained by Hashicorp and can therefore not be pulled in automatically by terraform. is not present in the - Bumps machine-config-operator to b3b074ee9156 (latest commit at the time of this writing). - Adds "github.com/clarketm/json" dependency for marshaling Ignition configs. This is a dropin replacement for "encoding/json" that supports zero values of structs with omittempty annotations when marshaling. In effect, this will exclude empty pointer struct fields from the marshaled data instead of inserting nil values into them, which do not pass openAPI validation on fields that are supposed to contain e.g. strings. The same library is used by machine-config-operator and ignition itself. - Updates the vendor dir to make commit idempotent. [1] https://github.com/coreos/ignition/blob/master/doc/configuration-v3_1.md [2] https://github.com/coreos/ignition/blob/master/doc/migrating-configs.md#from-version-230-to-300 Co-authored-by: Vadim Rutkovsky <vrutkovs@redhat.com>
2020-07-21 18:39:41 +02:00
github.com/ulikunitz/xz v0.5.7
Add go.mod
2020-02-14 00:00:06 +01:00
github.com/vincent-petithory/dataurl v0.0.0-20191104211930-d1553a71de50
vshpere: download ova into cache This change caches a copy of the vmware ova specified in rhcos.json in preperation to upload the OVA into a Template. Add vsphere terraform import ova - Using terraform-provider-vsphere as an example and source add a resource `vsphereprivate_import_ova`. - Modify existing terraform to use the above resource - Modify vsphere tfvars Co-authored-by: Jeremiah Stuever <jstuever@redhat.com>
2020-01-14 14:24:55 -08:00
github.com/vmware/govmomi v0.22.2
vendor: revendor terraform after dropping all backends Pins the terraform to https://github.com/openshift/hashicorp-terraform/tree/v0.12.20-openshift-3
2020-06-26 19:13:31 -07:00
github.com/xlab/treeprint v0.0.0-20181112141820-a009c3971eca // indirect
*: Migrate to ignition config spec v3.1 The installer now generates spec v3.1 ignition config, instead of v2.2 (and v2.4 for openstack) as before. The v3.1 ignition config specification can be found at [1]. A detailed overview of the differences between specs v2 and v3 can be found at [2]. Notable differences are: - the `Filesystem` identifier on ignition file configs no longer exists - `Overwrite` now defaults to `false` (was `true` in spec v2), which is why it is now set explicitly to keep the same behaviour. - duplicate file configs are now prohibited, i.e. all contents and all appendices must be defined in a single config. - duplicate systemd unit configs are now prohibited, i.e. the content and all dropins must be defined in a single config. This commit: - Bumps ignition to v2.3.0 with support for config spec v3.1. - Bumps terraform-provider-ignition to v2.1.0. Also adds downloading of the provider binary to `images/installer/Dockerfile.upi.ci` which is necessary because the ignition v2/spec3 version from the `community-terraform-providers/terraform-ignition-provider` fork is not present in the provider registry that is maintained by Hashicorp and can therefore not be pulled in automatically by terraform. is not present in the - Bumps machine-config-operator to b3b074ee9156 (latest commit at the time of this writing). - Adds "github.com/clarketm/json" dependency for marshaling Ignition configs. This is a dropin replacement for "encoding/json" that supports zero values of structs with omittempty annotations when marshaling. In effect, this will exclude empty pointer struct fields from the marshaled data instead of inserting nil values into them, which do not pass openAPI validation on fields that are supposed to contain e.g. strings. The same library is used by machine-config-operator and ignition itself. - Updates the vendor dir to make commit idempotent. [1] https://github.com/coreos/ignition/blob/master/doc/configuration-v3_1.md [2] https://github.com/coreos/ignition/blob/master/doc/migrating-configs.md#from-version-230-to-300 Co-authored-by: Vadim Rutkovsky <vrutkovs@redhat.com>
2020-07-21 18:39:41 +02:00
golang.org/x/crypto v0.0.0-20200429183012-4b2356b1ed79
vendor: updated terraform-provider-ironic version. The new TF provider will track will track installer-specific TF changes made to the baremetal platform
2020-04-08 10:23:17 -05:00
golang.org/x/lint v0.0.0-20200302205851-738671d3881b
baremetal: vendor: bump baremetal-operator This updates baremetal-operator to pull in the latest changes including hardware profiles. The installer vendors hardware profiles from baremetal-operator to keep the interface the same between terraform-provisioned baremetal hosts and those provisioned by the machine-api. This is done by updating the entry in the `replace` clause of the go.mod file. Then, we run `go mod tidy`, followed by `go mod vendor`. This breaks because the requested version of google.golang.org/grpc, v1.27.0, changes the API in backwards-incompatible ways. Thus, we also include a new pin for this dependency to the previously requested version, v1.25.0, which yields a working build.
2020-06-16 11:12:52 -03:00
golang.org/x/oauth2 v0.0.0-20200107190931-bf48bf16ab8d
*: Migrate to ignition config spec v3.1 The installer now generates spec v3.1 ignition config, instead of v2.2 (and v2.4 for openstack) as before. The v3.1 ignition config specification can be found at [1]. A detailed overview of the differences between specs v2 and v3 can be found at [2]. Notable differences are: - the `Filesystem` identifier on ignition file configs no longer exists - `Overwrite` now defaults to `false` (was `true` in spec v2), which is why it is now set explicitly to keep the same behaviour. - duplicate file configs are now prohibited, i.e. all contents and all appendices must be defined in a single config. - duplicate systemd unit configs are now prohibited, i.e. the content and all dropins must be defined in a single config. This commit: - Bumps ignition to v2.3.0 with support for config spec v3.1. - Bumps terraform-provider-ignition to v2.1.0. Also adds downloading of the provider binary to `images/installer/Dockerfile.upi.ci` which is necessary because the ignition v2/spec3 version from the `community-terraform-providers/terraform-ignition-provider` fork is not present in the provider registry that is maintained by Hashicorp and can therefore not be pulled in automatically by terraform. is not present in the - Bumps machine-config-operator to b3b074ee9156 (latest commit at the time of this writing). - Adds "github.com/clarketm/json" dependency for marshaling Ignition configs. This is a dropin replacement for "encoding/json" that supports zero values of structs with omittempty annotations when marshaling. In effect, this will exclude empty pointer struct fields from the marshaled data instead of inserting nil values into them, which do not pass openAPI validation on fields that are supposed to contain e.g. strings. The same library is used by machine-config-operator and ignition itself. - Updates the vendor dir to make commit idempotent. [1] https://github.com/coreos/ignition/blob/master/doc/configuration-v3_1.md [2] https://github.com/coreos/ignition/blob/master/doc/migrating-configs.md#from-version-230-to-300 Co-authored-by: Vadim Rutkovsky <vrutkovs@redhat.com>
2020-07-21 18:39:41 +02:00
golang.org/x/sys v0.0.0-20200509044756-6aff5f38e54f
vendor: bump golang.org/x/text to v0.3.3
2020-08-03 11:33:43 -07:00
golang.org/x/text v0.3.3 // indirect
vendor: bump gcp tf provider to v3.27.0
2020-06-26 19:21:04 -07:00
google.golang.org/api v0.25.0
*: Migrate to ignition config spec v3.1 The installer now generates spec v3.1 ignition config, instead of v2.2 (and v2.4 for openstack) as before. The v3.1 ignition config specification can be found at [1]. A detailed overview of the differences between specs v2 and v3 can be found at [2]. Notable differences are: - the `Filesystem` identifier on ignition file configs no longer exists - `Overwrite` now defaults to `false` (was `true` in spec v2), which is why it is now set explicitly to keep the same behaviour. - duplicate file configs are now prohibited, i.e. all contents and all appendices must be defined in a single config. - duplicate systemd unit configs are now prohibited, i.e. the content and all dropins must be defined in a single config. This commit: - Bumps ignition to v2.3.0 with support for config spec v3.1. - Bumps terraform-provider-ignition to v2.1.0. Also adds downloading of the provider binary to `images/installer/Dockerfile.upi.ci` which is necessary because the ignition v2/spec3 version from the `community-terraform-providers/terraform-ignition-provider` fork is not present in the provider registry that is maintained by Hashicorp and can therefore not be pulled in automatically by terraform. is not present in the - Bumps machine-config-operator to b3b074ee9156 (latest commit at the time of this writing). - Adds "github.com/clarketm/json" dependency for marshaling Ignition configs. This is a dropin replacement for "encoding/json" that supports zero values of structs with omittempty annotations when marshaling. In effect, this will exclude empty pointer struct fields from the marshaled data instead of inserting nil values into them, which do not pass openAPI validation on fields that are supposed to contain e.g. strings. The same library is used by machine-config-operator and ignition itself. - Updates the vendor dir to make commit idempotent. [1] https://github.com/coreos/ignition/blob/master/doc/configuration-v3_1.md [2] https://github.com/coreos/ignition/blob/master/doc/migrating-configs.md#from-version-230-to-300 Co-authored-by: Vadim Rutkovsky <vrutkovs@redhat.com>
2020-07-21 18:39:41 +02:00
google.golang.org/genproto v0.0.0-20200507105951-43844f6eee31
google.golang.org/grpc v1.29.1
Bump survey vendor for panic
2020-02-27 14:18:35 -05:00
gopkg.in/AlecAivazis/survey.v1 v1.8.9-0.20200217094205-6773bdf39b7f
Add go.mod
2020-02-14 00:00:06 +01:00
gopkg.in/ini.v1 v1.51.0
openstack: Upgrade the Terraform provider
2020-09-25 14:12:37 +02:00
gopkg.in/yaml.v2 v2.3.0
vendor: bump github.com/openshift/api version Bump to the latest github.com/openshift/api version in order to pick up changes to the infrastructure.config.openshift.io type for supporting other Azure cloud environments. Changes from openshift/api#650. https://issues.redhat.com/browse/CORS-1442
2020-05-20 12:27:56 -04:00
k8s.io/api v0.18.3
vendor: add controller-tools to vendor
2020-04-30 16:46:14 -07:00
k8s.io/apiextensions-apiserver v0.18.2
vendor: bump github.com/openshift/api version Bump to the latest github.com/openshift/api version in order to pick up changes to the infrastructure.config.openshift.io type for supporting other Azure cloud environments. Changes from openshift/api#650. https://issues.redhat.com/browse/CORS-1442
2020-05-20 12:27:56 -04:00
k8s.io/apimachinery v0.18.3
Add go.mod
2020-02-14 00:00:06 +01:00
k8s.io/client-go v12.0.0+incompatible
k8s.io/klog v1.0.0
Ensure AWS PublicIP is omitted from MachineSet when empty
2020-05-05 15:26:56 +01:00
k8s.io/utils v0.0.0-20200327001022-6496210b90e8
Add go.mod
2020-02-14 00:00:06 +01:00
sigs.k8s.io/cluster-api-provider-aws v0.0.0
sigs.k8s.io/cluster-api-provider-azure v0.0.0
sigs.k8s.io/cluster-api-provider-openstack v0.0.0
vendor: bump gcp tf provider to v3.27.0
2020-06-26 19:21:04 -07:00
sigs.k8s.io/controller-tools v0.3.1-0.20200617211605-651903477185
Add go.mod
2020-02-14 00:00:06 +01:00
)
replace (
Upgrade terraform-provider-azurerm to v2.8.0 from the openshift fork
2020-04-29 17:57:45 -03:00
github.com/Azure/go-autorest => github.com/tombuildsstuff/go-autorest v14.0.1-0.20200416184303-d4e299a3c04a+incompatible
github.com/Azure/go-autorest/autorest => github.com/tombuildsstuff/go-autorest/autorest v0.10.1-0.20200416184303-d4e299a3c04a
github.com/Azure/go-autorest/autorest/azure/auth => github.com/tombuildsstuff/go-autorest/autorest/azure/auth v0.4.3-0.20200416184303-d4e299a3c04a
Add go.mod
2020-02-14 00:00:06 +01:00
github.com/go-log/log => github.com/go-log/log v0.1.1-0.20181211034820-a514cf01a3eb // Pinned by MCO
vendor: bump to fix tf panic on mac OS Brings in vendor update for https://github.com/openshift/hashicorp-terraform/pull/4
2020-07-13 18:21:13 -07:00
github.com/hashicorp/terraform => github.com/openshift/terraform v0.12.20-openshift-4 // Pin to fork with deduplicated rpc types v0.12.20-openshift-4
vendor: bump terraform-plugin-sdk to version v1.14.0
2020-07-01 20:35:01 -07:00
github.com/hashicorp/terraform-plugin-sdk => github.com/openshift/hashicorp-terraform-plugin-sdk v1.14.0-openshift // Pin to fork with public rpc types
baremetal: revendor baremetal-operator to include the boot mode field This change updates the BareMetalHost type to include the new BootMode field. update go.mod; go mod vendor; go mod tidy Signed-off-by: Doug Hellmann <dhellmann@redhat.com>
2020-07-23 15:45:19 -04:00
github.com/metal3-io/baremetal-operator => github.com/openshift/baremetal-operator v0.0.0-20200715132148-0f91f62a41fe // Use OpenShift fork
Add go.mod
2020-02-14 00:00:06 +01:00
github.com/metal3-io/cluster-api-provider-baremetal => github.com/openshift/cluster-api-provider-baremetal v0.0.0-20190821174549-a2a477909c1d // Pin OpenShift fork
vendor: bump github.com/openshift/api version Bump to the latest github.com/openshift/api version in order to pick up changes to the infrastructure.config.openshift.io type for supporting other Azure cloud environments. Changes from openshift/api#650. https://issues.redhat.com/browse/CORS-1442
2020-05-20 12:27:56 -04:00
github.com/openshift/api => github.com/openshift/api v0.0.0-20200601094953-95abe2d2f422 // Pin API
Revendor after updating MAO
2020-04-29 15:21:57 +02:00
github.com/openshift/client-go => github.com/openshift/client-go v0.0.0-20200116152001-92a2713fa240 // Pin client-go
*: Migrate to ignition config spec v3.1 The installer now generates spec v3.1 ignition config, instead of v2.2 (and v2.4 for openstack) as before. The v3.1 ignition config specification can be found at [1]. A detailed overview of the differences between specs v2 and v3 can be found at [2]. Notable differences are: - the `Filesystem` identifier on ignition file configs no longer exists - `Overwrite` now defaults to `false` (was `true` in spec v2), which is why it is now set explicitly to keep the same behaviour. - duplicate file configs are now prohibited, i.e. all contents and all appendices must be defined in a single config. - duplicate systemd unit configs are now prohibited, i.e. the content and all dropins must be defined in a single config. This commit: - Bumps ignition to v2.3.0 with support for config spec v3.1. - Bumps terraform-provider-ignition to v2.1.0. Also adds downloading of the provider binary to `images/installer/Dockerfile.upi.ci` which is necessary because the ignition v2/spec3 version from the `community-terraform-providers/terraform-ignition-provider` fork is not present in the provider registry that is maintained by Hashicorp and can therefore not be pulled in automatically by terraform. is not present in the - Bumps machine-config-operator to b3b074ee9156 (latest commit at the time of this writing). - Adds "github.com/clarketm/json" dependency for marshaling Ignition configs. This is a dropin replacement for "encoding/json" that supports zero values of structs with omittempty annotations when marshaling. In effect, this will exclude empty pointer struct fields from the marshaled data instead of inserting nil values into them, which do not pass openAPI validation on fields that are supposed to contain e.g. strings. The same library is used by machine-config-operator and ignition itself. - Updates the vendor dir to make commit idempotent. [1] https://github.com/coreos/ignition/blob/master/doc/configuration-v3_1.md [2] https://github.com/coreos/ignition/blob/master/doc/migrating-configs.md#from-version-230-to-300 Co-authored-by: Vadim Rutkovsky <vrutkovs@redhat.com>
2020-07-21 18:39:41 +02:00
github.com/openshift/machine-config-operator => github.com/openshift/machine-config-operator v0.0.1-0.20200721120235-b3b074ee9156 // Pin MCO so it doesn't get downgraded
vendor: bump terraform-provider-aws to to version v2.67.0
2020-07-01 20:37:52 -07:00
github.com/terraform-providers/terraform-provider-aws => github.com/openshift/terraform-provider-aws v1.60.1-0.20200630224953-76d1fb4e5699 // Pin to openshift fork with tag v2.67.0-openshift
vendor: bump terraform-provider-azure to version v2.17.0
2020-07-07 09:40:31 -07:00
github.com/terraform-providers/terraform-provider-azurerm => github.com/openshift/terraform-provider-azurerm v1.40.1-0.20200707062554-97ea089cc12a // release-2.17.0 branch
*: Migrate to ignition config spec v3.1 The installer now generates spec v3.1 ignition config, instead of v2.2 (and v2.4 for openstack) as before. The v3.1 ignition config specification can be found at [1]. A detailed overview of the differences between specs v2 and v3 can be found at [2]. Notable differences are: - the `Filesystem` identifier on ignition file configs no longer exists - `Overwrite` now defaults to `false` (was `true` in spec v2), which is why it is now set explicitly to keep the same behaviour. - duplicate file configs are now prohibited, i.e. all contents and all appendices must be defined in a single config. - duplicate systemd unit configs are now prohibited, i.e. the content and all dropins must be defined in a single config. This commit: - Bumps ignition to v2.3.0 with support for config spec v3.1. - Bumps terraform-provider-ignition to v2.1.0. Also adds downloading of the provider binary to `images/installer/Dockerfile.upi.ci` which is necessary because the ignition v2/spec3 version from the `community-terraform-providers/terraform-ignition-provider` fork is not present in the provider registry that is maintained by Hashicorp and can therefore not be pulled in automatically by terraform. is not present in the - Bumps machine-config-operator to b3b074ee9156 (latest commit at the time of this writing). - Adds "github.com/clarketm/json" dependency for marshaling Ignition configs. This is a dropin replacement for "encoding/json" that supports zero values of structs with omittempty annotations when marshaling. In effect, this will exclude empty pointer struct fields from the marshaled data instead of inserting nil values into them, which do not pass openAPI validation on fields that are supposed to contain e.g. strings. The same library is used by machine-config-operator and ignition itself. - Updates the vendor dir to make commit idempotent. [1] https://github.com/coreos/ignition/blob/master/doc/configuration-v3_1.md [2] https://github.com/coreos/ignition/blob/master/doc/migrating-configs.md#from-version-230-to-300 Co-authored-by: Vadim Rutkovsky <vrutkovs@redhat.com>
2020-07-21 18:39:41 +02:00
github.com/terraform-providers/terraform-provider-ignition/v2 => github.com/community-terraform-providers/terraform-provider-ignition/v2 v2.1.0
vendor/terraform-provider-vsphere: DiskPostCloneOperation patch carry Updated openshift fork which contains the patch for DiskPostCloneOperation (https://github.com/openshift/terraform-provider-vsphere/pull/3)
2020-08-17 14:39:17 -04:00
github.com/terraform-providers/terraform-provider-vsphere => github.com/openshift/terraform-provider-vsphere v1.18.1-openshift-2
vendor: replace terraform-provider-vsphere with OpenShift fork With https://bugzilla.redhat.com/show_bug.cgi?id=1825323 we see terraform failing with an inconsistent plan when the vSAN storage policy enforces thin-provisioned disks but for some reason the terraform provider produces a plan stating they are thick-provisioned. Terraform docs indicates these types of problems require a fix to CustomizeDiff in the provider: https://www.terraform.io/docs/extend/terraform-0.12-compatibility.html#inaccurate-plans In a recent PR https://github.com/terraform-providers/terraform-provider-vsphere/pull/1052 we see that when the VM is being imported from an OVA, the DiskDiffOperation is simply skipped. DiskDiffOperation is the function that produces the inconsistent plan in the bugzilla mentioned before. We have created a similar PR to skip DiskDiffOperation when VMs are being cloned: https://github.com/terraform-providers/terraform-provider-vsphere/pull/1075 This commit carries that patch until it has merged upstream or resolved otherwise The commit was created by running: go mod edit -replace github.com/terraform-providers/terraform-provider-vsphere=github.com/openshift/terraform-provider-vsphere@v1.18.1-openshift-1 go mod edit -replace github.com/vmware/govmomi=github.com/vmware/govmomi@v0.22.2-0.20200420222347-5fceac570f29 go mod tidy go mod vendor This commit also updates the vsphereprivate provider to use the updated libraries.
2020-05-19 11:29:30 -04:00
github.com/vmware/govmomi => github.com/vmware/govmomi v0.22.2-0.20200420222347-5fceac570f29
Add go.mod
2020-02-14 00:00:06 +01:00
k8s.io/api => k8s.io/api v0.17.1 // Replaced by MCO/CRI-O
k8s.io/apiextensions-apiserver => k8s.io/apiextensions-apiserver v0.17.1 // Replaced by MCO/CRI-O
k8s.io/apimachinery => k8s.io/apimachinery v0.17.1 // Replaced by MCO/CRI-O
k8s.io/apiserver => k8s.io/apiserver v0.17.1 // Replaced by MCO/CRI-O
k8s.io/cli-runtime => k8s.io/cli-runtime v0.17.1 // Replaced by MCO/CRI-O
k8s.io/client-go => k8s.io/client-go v0.17.1 // Replaced by MCO/CRI-O
k8s.io/cloud-provider => k8s.io/cloud-provider v0.17.1 // Replaced by MCO/CRI-O
k8s.io/cluster-bootstrap => k8s.io/cluster-bootstrap v0.17.1 // Replaced by MCO/CRI-O
k8s.io/code-generator => k8s.io/code-generator v0.17.1 // Replaced by MCO/CRI-O
k8s.io/component-base => k8s.io/component-base v0.17.1 // Replaced by MCO/CRI-O
k8s.io/cri-api => k8s.io/cri-api v0.17.1 // Replaced by MCO/CRI-O
k8s.io/csi-translation-lib => k8s.io/csi-translation-lib v0.17.1 // Replaced by MCO/CRI-O
k8s.io/kube-aggregator => k8s.io/kube-aggregator v0.17.1 // Replaced by MCO/CRI-O
k8s.io/kube-controller-manager => k8s.io/kube-controller-manager v0.17.1 // Replaced by MCO/CRI-O
k8s.io/kube-proxy => k8s.io/kube-proxy v0.17.1 // Replaced by MCO/CRI-O
k8s.io/kube-scheduler => k8s.io/kube-scheduler v0.17.1 // Replaced by MCO/CRI-O
k8s.io/kubectl => k8s.io/kubectl v0.17.1 // Replaced by MCO/CRI-O
k8s.io/kubelet => k8s.io/kubelet v0.17.1 // Replaced by MCO/CRI-O
k8s.io/kubernetes => k8s.io/kubernetes v1.17.1 // Replaced by MCO/CRI-O
k8s.io/legacy-cloud-providers => k8s.io/legacy-cloud-providers v0.17.1 // Replaced by MCO/CRI-O
k8s.io/metrics => k8s.io/metrics v0.17.1 // Replaced by MCO/CRI-O
k8s.io/sample-apiserver => k8s.io/sample-apiserver v0.17.1 // Replaced by MCO/CRI-O
Ensure AWS PublicIP is omitted from MachineSet when empty
2020-05-05 15:26:56 +01:00
sigs.k8s.io/cluster-api-provider-aws => github.com/openshift/cluster-api-provider-aws v0.2.1-0.20200506073438-9d49428ff837 // Pin OpenShift fork
Add go.mod
2020-02-14 00:00:06 +01:00
sigs.k8s.io/cluster-api-provider-azure => github.com/openshift/cluster-api-provider-azure v0.1.0-alpha.3.0.20200120114645-8a9592f1f87b // Pin OpenShift fork
openstack: Pass the master server group by name Create the Control Plane server group in Terraform and pass the server group by name, and not by UUID, in the machine spec.
2020-05-26 10:04:30 +02:00
sigs.k8s.io/cluster-api-provider-openstack => github.com/openshift/cluster-api-provider-openstack v0.0.0-20200526112135-319a35b2e38e // Pin OpenShift fork
Add go.mod
2020-02-14 00:00:06 +01:00
)
Copy Permalink