W. Trevor King 18ca912897 pkg/destroy/libvirt: Use prefix-based deletion ...

To avoid wiping out the caller's whole libvirt environment, regardless
of whether it was associated with our cluster or not.  Using
cluster-name prefixes still makes me a bit jumpy, so I've added
warnings to both the environment-variable and asset-prompt docs
warning libvirt users to pick something sufficiently unique.

Also:

* Use {cluster-name}-master-{count} naming.  We used to use
  master{count}, which diverged from other usage (e.g. AWS, which has
  used master-{count} since way back in ca443c5e (openstack/nova:
  replace cloud-init with ignition, 2017-02-27,
  coreos/tectonic-installer#7).

* Rename module.libvirt_base_volume -> module.volume.  There's no
  reason to diverge from the module source for that name.

2018-11-13 14:52:48 -08:00

..

data

pkg/destroy/libvirt: Use prefix-based deletion

2018-11-13 14:52:48 -08:00

.gitignore

data: Setup a new data package

2018-09-25 23:32:10 -07:00

assets_generate.go

data: Setup a new data package

2018-09-25 23:32:10 -07:00

assets.go

data: Setup a new data package

2018-09-25 23:32:10 -07:00

unpack_test.go

pkg/asset/cluster: Only unpack the Terraform we need

2018-09-27 23:32:50 -07:00

unpack.go

pkg/asset/cluster: Only unpack the Terraform we need

2018-09-27 23:32:50 -07:00