coreos/terraform-provider-ct

Name: terraform-provider-ct

Owner: CoreOS

Description: Terraform provider for Container Linux Configs

Created: 2016-08-15 21:19:53.0

Updated: 2018-05-15 08:33:19.0

Pushed: 2018-04-25 23:36:20.0

Homepage:

Size: 1993

Language: Go

GitHub Committers

User	Most Recent Commit	# Commits

Other Committers

User	Email	Most Recent Commit	# Commits

README

Terraform Provider for Container Linux Configs

The ct provider provides a ct_config data source that parses a Container Linux Config, validates the content, and renders Ignition. The rendered strings can be used as input to other Terraform resources (e.g. user-data for instances).

Ignition schema output

Each minor version of terraform-provider-ct is tightly coupled with a minor version of the Ignition schema. Ignition transparently handles old Ignition schema versions, so this isn't normally an issue.

However, it is not safe to upgrade between minor versions on existing managed clusters. Minor version upgrades of this plugin will re-provision your cluster because the Ignition config output has changed.

| terraform-provider-ct | Ignition schema version | | ———————– | ———————– | | 0.2.x | 2.0 | | 0.3.x | 2.2 |

Requirements

• Terraform 0.9.x

Installation

Add the terraform-provider-ct plugin binary on your filesystem.

v
et -u github.com/coreos/terraform-provider-ct

Register the plugin in ~/.terraformrc.

iders {
 = "/$GOPATH/bin/terraform-provider-ct"

Usage

 "ct_config" "worker" {
ntent      = "${file("worker.yaml")}"
atform     = "ec2"
etty_print = false

ippets = [
"${file("units.yaml")}",
"${file("storage.yaml")}",



urce "aws_instance" "worker" {
er_data = "${data.ct_config.worker.rendered}"

The optional platform can be “azure”, “ec2”, “gce”, or others to perform platform-specific susbstitutions. By default, platform is “” (none, for bare-metal).

The snippets field is an optional list of Container Linux Config snippets that are appended to the main config specified in content before being rendered into an Ignition config.

Development

To develop the provider plugin locally, set up Go 1.8+ and a valid GOPATH. Build the plugin locally.

Optionally, install the plugin to $(GOPATH)/bin.

 install

Vendor

Add or update dependencies in glide.yaml and vendor. The glide and glide-vc tools vendor and prune dependencies.

 vendor