You might find the user_add job from os-conf-release useful. It allows custom users to be added using either password or key-based authentication. For example, the following would allow SSH login and

I think this was a bug which was fixed in a later version. Try upgrading your director to a newer version.

Hi - sounds like two issues. First, update jq to a newer version from stedolan.github.com/jq. Second, it sounds like you're missing boosh - make sure you've gone through the Setting Up Local Dependenc

Make sure your pre-start script will exit with an error if a command fails (like `set -e`). I would guess your pre-start script is calling `monit start {job-name}`, but that will error since the jobs

I'm not familiar with that particular blog entry, but the error you mention suggests your YAML file is invalid. Perhaps double check that you're indenting with spaces instead of tabs and using the cor

If you really, really need the functionality, you could try setting a value greater than 1 (e.g. 2); by code it seems like that hack might help. Wouldn't recommend it in any sort of non-test environme

Hi - the login job was removed in v214 and documented in the release notes [1]. You should also review the other release notes [2] to know what else may affect your deployment in the upgrade. [1] http

Should work with the default, `c1oudc0w` password. Could also double check that you're not overriding the default password via the `env.bosh.password` setting in your compilation VMs in your manifests

You can use mkpasswd. The value is in the format of ${hash}${salt}${data}. echo -n 'my-insecure-password' | mkpasswd --method=md5 --password-fd=0 $1$AiNuFf.t$1qIrn6JEoJIvcKS.jQyK50 If you don't really

Hi Akhil - make sure you have updated all references in your bosh manifest to point to us-west-1 (bosh.io examples use us-east-1). It looks like bosh-init thinks you're trying to work in us-east-1 - i