temporarily disable failing bat test
[cli_plugin_micro] check that ip is non-nil in discover_bosh_ip
Always create the SSL config for the director Nginx

Since the Nginx startup script creates the self-signed certificates by
default we should always use SSL even if the user does not specify a key
in their configuration. This is a problem because the CLI will always
try to use SSL now.
Don't error if the subject of a loaded cert doesn't match
Several fixes

- Correct aws generate bosh command description
- Increase sleep time when deletting vpcs
- Add DataDog api keys in full bosh template
- HealthMonitor needs to use https when talking to director
don't fetch existing S3 gems before generating the index
[agent] Fallback to user_data injected file for OpenStack

- If agent cannot get user data from the OpenStack user data service,
  then fallback to the user_data injected file.
- Added some more unit tests to OpenStack registry.
- Refactored the OpenStack Registry and Settings.
Merge pull request #149 from cloudfoundry/openstack_agent

[agent] Fallback to user_data injected file for OpenStack
[release] Fix director ssl configuration when no certs are provided
Merge pull request #150 from cloudfoundry/fix-ssl

[release] Fix director ssl configuration when no certs are provided
Try to delete the disk after deleting the VM it is attached to
Default the retryable sleep to use exponential backoff
Fix typo in error message
Health monitor should use SSL when director is using SSL.

[closes #42401181 & #42401209]
Revert "Health monitor should use SSL when director is using SSL."

If you do not set 'director.encryption' then the director does not try
and use SSL but some things are hard-coded to use SSL now. This is
breaking things. Reverting until we can fix.

This reverts commit 5788c9175bced1b5b1e3264233d14741be040664.
Make health monitor use SSL to director all the time.

[fixes #42401181 #42401209]
NAT box uses 10.10.0.10 so we should not try and use it
Enable health monitor resurrector on bootstrap

* MicroBosh and Bosh bootstrap will always create a new admin user and
  hm user
* Waits for director to become available before attempting login during
  full bosh bootstrap
[Finishes #48844663]
Cleaned up bosh_cli_plugin_aws functional tests
Generated manifests should have required health manager credentials