Question: has anyone else come across this? I'm getting an error when I'm trying to create a product display. It happens when I'm trying to put in the product SKU.

> 
> An AJAX HTTP error occurred.
> 
> 
> HTTP Result Code: 200
> 
> 
> Debugging information follows.
> 
> 
> Path: <http://hayfield.com:8082/commerce_product/autocomplete/node/field_product/product_display>
> 
> 
> StatusText: OK
> 
> 
> ResponseText: `{"glorious_dream":"\u003Cdiv class=\u0022reference-autocomplete\u0022\u003Eglorious_dream: Glorious Dream\u003C\u002Fdiv\u003E", "Hayfield_Elegance":"\u003Cdiv class=\u0022reference-autocomplete\u0022\u003EHayfield_Elegance: Hayfield Elegance\u003C\u002Fdiv\u003E"}jQuery.extend(Drupal.settings, {"thmr_1":{"id":"thmr_1", "name":"link", "used":"theme_link", "type":"func", "duration":2.78, "candidates":[ "hayfield_link" ], "preprocessors":[ ], "processors":[ ]}, "request_id":"1852760308506e2eabeea31", "devel_themer_uri":"\u002Fdevel_themer\u002Fvariables\u002F1852760308506e2eabeea31"});`
> 
> 
> 

Thanks in advance!!

Answer: 
Yes. The short answer is you update your Drush make file to point to the new version of the module you want to be included in your new platform(build).

In your drush make file you would include the version of each module you are including in your platform build. So views for example would look like this.

```
projects[views][subdir] = "contrib"
projects[views][version] = "3.4"

```

Now if you want to update to the new version of Views module you would update your make file to something like this.

```
projects[views][subdir] = "contrib"
projects[views][version] = "3.5"

```

Then build a new platform in Aegir using this updated drush make file. Then you would migrate the site to the new platform and Aegir will do the update for you.

It's a pretty slick workflow. I keep all of my drush make files in a repo called builds so I can have a record of each build of a project. Hope that helps.
Bob beat me to it :) but in response to this and your email you sent me, yes indeed this is the correct procedure. Treat your Drush makefile as the 'blueprint' of your application. 

Work away in development manually / clone your live site and manually 'drush up' or 'drush dl' a module and test that everything works as expected.

Then fold that new module/updated version into your makefile, build a new platform each time the makefile is updated, and use the 'Migrate' task to 'upgrade' your application onto the target platform. 

If something goes wrong during the upgrade (e.g during the drush updatedb which occurs during a Migration to apply schema updates in your database), Aegir will, in most cases, automatically roll back to the previous platform, which is the appeal of such a system.