Make it a variable so we only need to update it once per version bump. We
can automate it later.
On Dec 20, 2013 4:36 PM, "robszumski" <notifications@github.com> wrote:

> In running-coreos/cloud-providers/brightbox/index.md:
>
> > +
> > +You can use any random string so we’ll use the `uuid` tool here to generate one:
> > +
> > +```
> > +$ TOKEN=`uuid`
> > +
> > +$ echo $TOKEN
> > +53cf11d4-3726-11e3-958f-939d4f7f9688
> > +```
> > +
> > +Then build three servers using the image, in the server group we created and specifying the token as the user data:
> > +
> > +```
> > +$ brightbox servers create -i 3 --type small --name "coreos" --user-data $TOKEN --server-groups grp-cdl6h img-9ogji
> > +
> > +Creating 3 small (typ-8fych) servers with image CoreOS 94.0.0 (img-9ogji) in groups grp-cdl6h with 0.05k of user data
>
> Isn't that going to be on their schedule? if we write a script, how do we
> sync it with the version of the image they pulled?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/coreos/docs/pull/77/files#r8515247>
> .
>