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

158 lines
9.4 KiB
Modula-2
Raw Normal View History

2020-02-14 00:00:06 +01:00
module github.com/openshift/installer
go 1.14
2020-02-14 00:00:06 +01:00
require (
2020-10-19 11:20:18 +03:00
cloud.google.com/go v0.65.0
github.com/AlecAivazis/survey/v2 v2.2.12
github.com/Azure/azure-sdk-for-go v51.2.0+incompatible
github.com/Azure/go-autorest/autorest v0.11.17
github.com/Azure/go-autorest/autorest/adal v0.9.10
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.4.0
2020-02-14 00:00:06 +01:00
github.com/Azure/go-ntlmssp v0.0.0-20191115210519-2b2be6cc8ed4 // indirect
github.com/ChrisTrenkamp/goxpath v0.0.0-20190607011252-c5096ec8773d // indirect
ibmcloud: Add scaffolding for the IBM Cloud platform ibmcloud: add ibm cloud types support the new ibm cloud platform by adding required types ibmcloud: add initial assets Add ibmcloud assets to support the new ibmcloud platform. These changes are functional, but additional functionality will be built out over time ibmcloud: resolve linting issues ibmcloud: obtain the cisInstanceCRN for install-config The cisInstanceCRN field is derived from the user-provided baseDomain. It is needed for all DNS configuration. types: fix ibmcloud machinepool file name ibmcloud: rename platform ResourceGroupID field Rename the field `ResourceGroupID` in the Platform type to `ResourceGroup` ibmcloud: add initial metadata ibmcloud: add ClusterOSImage customization The ClusterOSImage field will allow the user to specify the custom RHCOS image to use for their cluster VSIs ibmcloud: add fields to Platform type Add the DefaultMachinePlatform, VPC, VPCResourceGroup, and Subnets fields to the Platform type. These are needed to fully define a cluster. ibmcloud: improve platform validation and tests Add in additional validation to the ibmcloud Platform. Also, add unit tests around that new validation. This is just a start and more validation and unit tests are required. ibmcloud: fix linting issues These issues were discovered using golangci-lint ibmcloud: use resource group name in install config Use the resource group name instead of ID in the install config. This will be more human friendly. The ID will also still be valid, but name will be preferred. ibmcloud: improve default resource group check Check for the default resource group based off of the 'default' field in the resource group struct. ibmcloud: fix typo ibmcloud: remove vpcResourceGroup and use vpc ID vpcResourceGroup is no longer needed if the vpc field holds the ID of the VPC instead of the name. ibmcloud: enforce clusterOSImage region The clusterOSImage refers to a custom image in a user's VPC. That image is regionally scoped and the region should be honored. Users should not be allowed to pick a custom image from a region that differes from the value of the region field in the install config. ibmcloud: use resourcev2 API The resourcev2 API should be used in place of v1. This is the most up-to-date and well supported version. ibmcloud: fix log message Co-Authored-By: Hidematsu Sueki <Hidematsu.Sueki@ibm.com> ibmcloud: add machinepool type and validation Add the MachinePool type for the IBM Cloud platform. Also include initial validation on the fields. ibmcloud: update survey version ibmcloud: use ibm go sdks instead of bluemix-go The ibm-go-sdk and corresponding service SDKs in the IBM GH org are more up-to-date and routinely supported. The old bluemix-go SDKs should no longer be used. update go mod update vendor fix: make validateVPCConfig a private function Co-authored-by: Matthew Staebler <staebler@redhat.com> fix: improve log message for resource group not found Co-authored-by: Matthew Staebler <staebler@redhat.com> fix: simplify subnet return statement Co-authored-by: Matthew Staebler <staebler@redhat.com> fix: improve log message for vpc not found Co-authored-by: Matthew Staebler <staebler@redhat.com> fix: images slice declaration Co-authored-by: Matthew Staebler <staebler@redhat.com> fix: improve images range loop Co-authored-by: Matthew Staebler <staebler@redhat.com> fix: typo in baseDomain help string Co-authored-by: Matthew Staebler <staebler@redhat.com> fix: clarify resource group help message fix: use platformPath as variable name Co-authored-by: Matthew Staebler <staebler@redhat.com> fix: ibmcloud platform reference Co-authored-by: Matthew Staebler <staebler@redhat.com> fix: remove unnecessary conditionals in validation fix: check encryptionKey exists before validation fix: improve zone validation message Co-authored-by: Matthew Staebler <staebler@redhat.com> fix: keep errors out of happy path fix: add index to subnets validation fix: create VPCResourceNotFoundError fix: use sets.String for contains fix: ibmcloud platform type comments fix: improve vpc config validation messages fix: add omitempty for encryptionKey Co-authored-by: Matthew Staebler <staebler@redhat.com> fix: improve BootVolume copying Co-authored-by: Matthew Staebler <staebler@redhat.com> fix: rename MachinePool.Type to InstanceType fix: remove validateRegion fix: remove unnecessary context from client fix: remove context timeout in ic Platform fix: remove superfluous edit fix: update unit tests fix: move types used by cilent to same package fix: update OWNERS and OWNERS_ALIASES fix: improve client call to load services fix: improve GetZoneIDByName range loop fix: whitepsace in OWNERS fix: populate ibmcloud OWNERS_ALIASES fix: make cisServiceID a const Co-authored-by: Matthew Staebler <staebler@redhat.com> ibmcloud: refactor resource groups Allow users to have VPC resources in a different resource group from the cluster creation. This will enable CI and E2E testing along with making it easier to destroy clusters. This commit also adds a "Name" suffix to resource groups to align with other platforms naming convention. fix: error message format fix: update unit test ibmcloud: move ibmcloud to hidden platforms The IBMCloud platform will be in a developer preview for 4.9. As a result we will move it to the list of hidden platforms. This commit does that by default, but allows for it to show up in the survey via a build flag: 'ibmcloud'. ibmcloud: remove cisInstanceCRN field The cisInstanceCRN platform field is not needed. Though it is possible to manage a single DNS zone with multiple CIS instances, only one zone can be in the "Active" state at a time. As a result, we know which CIS instance to use based off of its managed zone's state. fix: address pr comments update codegen
2021-04-15 14:51:26 -04:00
github.com/IBM-Cloud/bluemix-go v0.0.0-20210513052039-9ddb92888817
github.com/IBM/go-sdk-core/v5 v5.4.3
github.com/IBM/networking-go-sdk v0.14.0
github.com/IBM/platform-services-go-sdk v0.18.13
github.com/IBM/vpc-go-sdk v1.0.1
2020-02-14 00:00:06 +01:00
github.com/Netflix/go-expect v0.0.0-20190729225929-0e00d9168667 // indirect
github.com/antchfx/xpath v1.1.2 // indirect
2020-10-19 11:20:18 +03:00
github.com/apparentlymart/go-cidr v1.1.0
2020-02-14 00:00:06 +01:00
github.com/awalterschulze/gographviz v0.0.0-20190522210029-fa59802746ab
github.com/aws/aws-sdk-go v1.35.20
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
2020-02-14 00:00:06 +01:00
github.com/containers/image v3.0.2+incompatible
github.com/coreos/ignition/v2 v2.9.0
github.com/coreos/stream-metadata-go v0.0.0-20210225230131-70edb9eb47b3
github.com/dmacvicar/terraform-provider-libvirt v0.6.4-0.20201216193629-2b60d7626ff8
github.com/fatih/color v1.10.0 // indirect
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
github.com/go-playground/validator/v10 v10.2.0
2020-10-19 11:20:18 +03:00
github.com/golang/mock v1.4.4
github.com/golang/protobuf v1.4.3
github.com/google/martian v2.1.1-0.20190517191504-25dcb96d9e51+incompatible // indirect
ibmcloud: Add scaffolding for the IBM Cloud platform ibmcloud: add ibm cloud types support the new ibm cloud platform by adding required types ibmcloud: add initial assets Add ibmcloud assets to support the new ibmcloud platform. These changes are functional, but additional functionality will be built out over time ibmcloud: resolve linting issues ibmcloud: obtain the cisInstanceCRN for install-config The cisInstanceCRN field is derived from the user-provided baseDomain. It is needed for all DNS configuration. types: fix ibmcloud machinepool file name ibmcloud: rename platform ResourceGroupID field Rename the field `ResourceGroupID` in the Platform type to `ResourceGroup` ibmcloud: add initial metadata ibmcloud: add ClusterOSImage customization The ClusterOSImage field will allow the user to specify the custom RHCOS image to use for their cluster VSIs ibmcloud: add fields to Platform type Add the DefaultMachinePlatform, VPC, VPCResourceGroup, and Subnets fields to the Platform type. These are needed to fully define a cluster. ibmcloud: improve platform validation and tests Add in additional validation to the ibmcloud Platform. Also, add unit tests around that new validation. This is just a start and more validation and unit tests are required. ibmcloud: fix linting issues These issues were discovered using golangci-lint ibmcloud: use resource group name in install config Use the resource group name instead of ID in the install config. This will be more human friendly. The ID will also still be valid, but name will be preferred. ibmcloud: improve default resource group check Check for the default resource group based off of the 'default' field in the resource group struct. ibmcloud: fix typo ibmcloud: remove vpcResourceGroup and use vpc ID vpcResourceGroup is no longer needed if the vpc field holds the ID of the VPC instead of the name. ibmcloud: enforce clusterOSImage region The clusterOSImage refers to a custom image in a user's VPC. That image is regionally scoped and the region should be honored. Users should not be allowed to pick a custom image from a region that differes from the value of the region field in the install config. ibmcloud: use resourcev2 API The resourcev2 API should be used in place of v1. This is the most up-to-date and well supported version. ibmcloud: fix log message Co-Authored-By: Hidematsu Sueki <Hidematsu.Sueki@ibm.com> ibmcloud: add machinepool type and validation Add the MachinePool type for the IBM Cloud platform. Also include initial validation on the fields. ibmcloud: update survey version ibmcloud: use ibm go sdks instead of bluemix-go The ibm-go-sdk and corresponding service SDKs in the IBM GH org are more up-to-date and routinely supported. The old bluemix-go SDKs should no longer be used. update go mod update vendor fix: make validateVPCConfig a private function Co-authored-by: Matthew Staebler <staebler@redhat.com> fix: improve log message for resource group not found Co-authored-by: Matthew Staebler <staebler@redhat.com> fix: simplify subnet return statement Co-authored-by: Matthew Staebler <staebler@redhat.com> fix: improve log message for vpc not found Co-authored-by: Matthew Staebler <staebler@redhat.com> fix: images slice declaration Co-authored-by: Matthew Staebler <staebler@redhat.com> fix: improve images range loop Co-authored-by: Matthew Staebler <staebler@redhat.com> fix: typo in baseDomain help string Co-authored-by: Matthew Staebler <staebler@redhat.com> fix: clarify resource group help message fix: use platformPath as variable name Co-authored-by: Matthew Staebler <staebler@redhat.com> fix: ibmcloud platform reference Co-authored-by: Matthew Staebler <staebler@redhat.com> fix: remove unnecessary conditionals in validation fix: check encryptionKey exists before validation fix: improve zone validation message Co-authored-by: Matthew Staebler <staebler@redhat.com> fix: keep errors out of happy path fix: add index to subnets validation fix: create VPCResourceNotFoundError fix: use sets.String for contains fix: ibmcloud platform type comments fix: improve vpc config validation messages fix: add omitempty for encryptionKey Co-authored-by: Matthew Staebler <staebler@redhat.com> fix: improve BootVolume copying Co-authored-by: Matthew Staebler <staebler@redhat.com> fix: rename MachinePool.Type to InstanceType fix: remove validateRegion fix: remove unnecessary context from client fix: remove context timeout in ic Platform fix: remove superfluous edit fix: update unit tests fix: move types used by cilent to same package fix: update OWNERS and OWNERS_ALIASES fix: improve client call to load services fix: improve GetZoneIDByName range loop fix: whitepsace in OWNERS fix: populate ibmcloud OWNERS_ALIASES fix: make cisServiceID a const Co-authored-by: Matthew Staebler <staebler@redhat.com> ibmcloud: refactor resource groups Allow users to have VPC resources in a different resource group from the cluster creation. This will enable CI and E2E testing along with making it easier to destroy clusters. This commit also adds a "Name" suffix to resource groups to align with other platforms naming convention. fix: error message format fix: update unit test ibmcloud: move ibmcloud to hidden platforms The IBMCloud platform will be in a developer preview for 4.9. As a result we will move it to the list of hidden platforms. This commit does that by default, but allows for it to show up in the survey via a build flag: 'ibmcloud'. ibmcloud: remove cisInstanceCRN field The cisInstanceCRN platform field is not needed. Though it is possible to manage a single DNS zone with multiple CIS instances, only one zone can be in the "Active" state at a time. As a result, we know which CIS instance to use based off of its managed zone's state. fix: address pr comments update codegen
2021-04-15 14:51:26 -04:00
github.com/google/uuid v1.2.0
github.com/gophercloud/gophercloud v0.17.0
github.com/gophercloud/utils v0.0.0-20210323225332-7b186010c04f
github.com/h2non/filetype v1.0.12
github.com/hashicorp/go-azure-helpers v0.13.0
2020-10-19 11:20:18 +03:00
github.com/hashicorp/go-plugin v1.3.0
2020-02-14 00:00:06 +01:00
github.com/hashicorp/logutils v1.0.0
2020-10-19 11:20:18 +03:00
github.com/hashicorp/terraform v0.13.4
github.com/hashicorp/terraform-plugin-sdk v1.16.0
github.com/hashicorp/terraform-provider-kubernetes v1.13.3
github.com/hashicorp/terraform-provider-vsphere v1.24.3
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
2020-10-19 11:20:18 +03:00
github.com/k8snetworkplumbingwg/network-attachment-definition-client v0.0.0-20191119172530-79f836b90111
github.com/kubevirt/terraform-provider-kubevirt v0.0.0-00010101000000-000000000000
2020-02-14 00:00:06 +01:00
github.com/libvirt/libvirt-go v5.10.0+incompatible
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-20210527161605-4e331bfd4b1d
2020-02-14 00:00:06 +01:00
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
github.com/openshift-metal3/terraform-provider-ironic v0.2.6
github.com/openshift/api v0.0.0-20210622200201-7740bfb97397
github.com/openshift/client-go v0.0.0-20201214125552-e615e336eb49
github.com/openshift/cloud-credential-operator v0.0.0-20200316201045-d10080b52c9e
github.com/openshift/cluster-api v0.0.0-20191030113141-9a3a7bbe9258
github.com/openshift/cluster-api-provider-gcp v0.0.1-0.20201203141909-4dc702fd57a5
github.com/openshift/cluster-api-provider-kubevirt v0.0.0-20201214114543-e5aed9c73f1f
2020-02-14 00:00:06 +01:00
github.com/openshift/cluster-api-provider-libvirt v0.2.1-0.20191219173431-2336783d4603
github.com/openshift/cluster-api-provider-ovirt v0.1.1-0.20210406154451-1ea59ab6b543
github.com/openshift/library-go v0.0.0-20201215165635-4ee79b1caed5
github.com/openshift/machine-api-operator v0.2.1-0.20210104142355-8e6ae0acdfcf
*: 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
github.com/ovirt/go-ovirt v0.0.0-20210308100159-ac0bcbc88d7c
github.com/ovirt/terraform-provider-ovirt v0.99.1-0.20210527150815-b3d4424a7da1
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/pkg/errors v0.9.1
github.com/pkg/sftp v1.10.1
github.com/prometheus/client_golang v1.9.0
github.com/prometheus/common v0.15.0
2020-02-14 00:00:06 +01:00
github.com/satori/uuid v1.2.0 // indirect
github.com/shurcooL/httpfs v0.0.0-20190707220628-8d4bc4ba7749 // indirect
2020-02-14 00:00:06 +01:00
github.com/shurcooL/vfsgen v0.0.0-20181202132449-6a9ea43bcacd
github.com/sirupsen/logrus v1.7.0
github.com/spf13/cobra v1.1.1
github.com/stretchr/testify v1.6.1
github.com/terraform-provider-openstack/terraform-provider-openstack v1.37.0
2020-10-19 11:20:18 +03:00
github.com/terraform-providers/terraform-provider-aws v1.60.1-0.20200807230610-d5346d47e3af
github.com/terraform-providers/terraform-provider-azurerm v1.44.1-0.20200911233120-57b2bfc9d42c
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
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
2020-10-19 11:20:18 +03:00
github.com/ulikunitz/xz v0.5.8
2020-02-14 00:00:06 +01:00
github.com/vincent-petithory/dataurl v0.0.0-20191104211930-d1553a71de50
github.com/vmware/govmomi v0.24.0
terraform: support separate tf into stages Add a Stage interface which defines a given terraform stage for a given platform. For each stage, there is an option to include the stage in the destroy when doing a bootstrap destroy. There is also an option to provide a custom destroy function. For example, when destroying the GCP bootstrap, there is a stage where the destroy behavior is modifying the load balancers to remove the bootstrap from the backend. Use the Stage interface to run the terraform applies and destroys. The outputs from each stage are used as input into subsequent stages. This allows stages to get information that would either not be available at all or only available via a data source. For example, with GCP there is a stage where the health check IDs are needed. There is no data source available in the gcp terraform provider for accessing these IDs. However, using the output from the stage where the health checks are created, the stage is able to get the health check IDs as input instead. Include the IPs of the bootstrap instance and the control plane instances in the output of the terraform stage where the instances are created. This is used by the bootstrap gather as a consistent way to grab the IPs as opposed to extracting the IPs from the terraform state files. When looking for the IPs of the bootstrap and control plane machines, consider all of the terraform stages. For compat stages, there is no change in behavior. For newer split stages, the gather looks through the output files for the "bootstrap_ip" and "control_plane_ips" outputs. https://issues.redhat.com/browse/CORS-1693
2021-04-26 19:49:17 -07:00
github.com/zclconf/go-cty v1.6.1
golang.org/x/crypto v0.0.0-20210220033148-5ea612d1eb83
golang.org/x/lint v0.0.0-20200302205851-738671d3881b
golang.org/x/mod v0.4.0 // indirect
2020-10-19 11:20:18 +03:00
golang.org/x/oauth2 v0.0.0-20200902213428-5d25da1a8d43
golang.org/x/sys v0.0.0-20210225134936-a50acf3fe073
google.golang.org/api v0.33.0
google.golang.org/genproto v0.0.0-20201110150050-8816d57aaa9a
2020-10-19 11:20:18 +03:00
google.golang.org/grpc v1.32.0
gopkg.in/ini.v1 v1.61.0
gopkg.in/yaml.v2 v2.4.0
k8s.io/api v0.21.1
k8s.io/apiextensions-apiserver v0.21.0-rc.0
k8s.io/apimachinery v0.21.1
2020-02-14 00:00:06 +01:00
k8s.io/client-go v12.0.0+incompatible
2020-10-22 11:01:37 -04:00
k8s.io/klog v1.0.0
k8s.io/klog/v2 v2.8.0
k8s.io/utils v0.0.0-20210111153108-fddb29f9d009
2020-10-19 11:20:18 +03:00
kubevirt.io/client-go v0.29.0
kubevirt.io/containerized-data-importer v1.10.9
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
sigs.k8s.io/controller-tools v0.4.1
2020-02-14 00:00:06 +01:00
)
replace (
cloud.google.com/go => cloud.google.com/go v0.57.0
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
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
github.com/hashicorp/terraform-plugin-sdk => github.com/openshift/hashicorp-terraform-plugin-sdk v1.14.0-openshift // Pin to fork with public rpc types
github.com/hashicorp/terraform-provider-vsphere => github.com/openshift/terraform-provider-vsphere v1.24.3-openshift
github.com/kubevirt/terraform-provider-kubevirt => github.com/nirarg/terraform-provider-kubevirt v0.0.0-20201222125919-101cee051ed3
github.com/metal3-io/baremetal-operator => github.com/openshift/baremetal-operator v0.0.0-20210527161605-4e331bfd4b1d // Use OpenShift fork
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
github.com/openshift/client-go => github.com/openshift/client-go v0.0.0-20200929181438-91d71ef2122c // Pin client-go
github.com/openshift/machine-config-operator => github.com/openshift/machine-config-operator v0.0.1-0.20201009041932-4fe8559913b8 // Pin MCO so it doesn't get downgraded
github.com/terraform-providers/terraform-provider-aws => github.com/openshift/terraform-provider-aws v1.60.1-0.20210622193531-7d13cfbb1a8c // Pin to openshift fork with tag v2.67.0-openshift-1
github.com/terraform-providers/terraform-provider-azurerm => github.com/openshift/terraform-provider-azurerm v1.44.1-0.20210224232508-7509319df0f4 // Pin to 2.48.0-openshift
*: 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
k8s.io/client-go => k8s.io/client-go v0.21.0-rc.0
k8s.io/kubectl => k8s.io/kubectl v0.21.0-rc.0
kubevirt.io/client-go => kubevirt.io/client-go v0.29.0
sigs.k8s.io/cluster-api-provider-aws => github.com/openshift/cluster-api-provider-aws v0.2.1-0.20210121023454-5ffc5f422a80
sigs.k8s.io/cluster-api-provider-azure => github.com/openshift/cluster-api-provider-azure v0.1.0-alpha.3.0.20201016155852-4090a6970205
sigs.k8s.io/cluster-api-provider-openstack => github.com/openshift/cluster-api-provider-openstack v0.0.0-20210302164104-8498241fa4bd
sigs.k8s.io/controller-runtime => sigs.k8s.io/controller-runtime v0.9.0-alpha.1
sigs.k8s.io/controller-tools => sigs.k8s.io/controller-tools v0.3.1-0.20200617211605-651903477185
2020-02-14 00:00:06 +01:00
)
2020-10-19 11:20:18 +03:00
// Prevent the following modules from upgrading version as result of terraform-provider-kubernetes module
// The following modules need to be locked to compile correctly with terraform-provider-azure and terraform-provider-google
replace (
github.com/apparentlymart/go-cidr => github.com/apparentlymart/go-cidr v1.0.1
github.com/aws/aws-sdk-go => github.com/aws/aws-sdk-go v1.32.3
github.com/go-openapi/spec => github.com/go-openapi/spec v0.19.4
github.com/hashicorp/go-plugin => github.com/hashicorp/go-plugin v1.2.2
github.com/ulikunitz/xz => github.com/ulikunitz/xz v0.5.7
google.golang.org/api => google.golang.org/api v0.25.0
google.golang.org/genproto => google.golang.org/genproto v0.0.0-20200526211855-cb27e3aa2013
google.golang.org/grpc => google.golang.org/grpc v1.29.1
)