The micro CLI plugin is deprecated and will be discontinued in a few months. bosh-init replaces its functionality and improves on its features. If you do not maintain a MicroBOSH VM, there is no need to do anything; however, if you do please follow these steps:

  1. Install bosh-init.

  2. Review Using bosh-init.

  3. Familiarize yourself with how to write a deployment manifest for the Director VM (previously referred to as MicroBOSH) following examples mentioned on one of these pages depending on your IaaS:

  4. Create a deployment manifest (for example bosh.yml) based on one of the above examples.

    Note: Make sure NATS, blobstore, and database settings used by the Director, registry, and DNS server match your previous configuration.

  5. Copy bosh-deployments.yml to the deployment directory that contains your new deployment manifest. bosh-deployments.yml is a state file produced and updated by the micro CLI. It contains VM and persistent disk IDs of your current MicroBOSH VM.

  6. Run bosh-init deploy ./bosh.yml. bosh-init will find bosh-deployments.yml in your deployment directory, convert it to a new deployment state file (in our example bosh-state.json) and update the Director VM as specified by deployment manifest.

  7. Save the deployment state file left in your deployment directory so you can later update/delete your Director. See Deployment state section of ‘Using bosh-init’ for more details.

  8. Target your Director with the BOSH CLI and run bosh deployments command to confirm your existing deployments were migrated.

Contribute changes to this page