Unable to update-environment on a EB Worker installation #40
Comments
|
I haven't looked at worker types yet. I expect to spend the next week doing some code maintenance and I expect to get back at you shortly Meanwhile, can you issue a call to describe-environments and send its output to me via email? It could help Thanks |
|
Amazing. Worker instances do not set cnamePrefix. It seems we need to bring back environmentName back into AbstractNeedsEnvironment. |
|
@dmessenger, should work out of the box from 1.2.0-SNAPSHOT (use sonatype-oss-snapshots as a repository) If you want to enable it for creation, this should work: The archetype also includes an example of an SQSD Listener. In theory, I've tested most aspects involved around it (create-environment, update-environment, terminate-environment and fast-deploy) Thanks. |
|
This no longer throws an exception with Environment Not Found.
Here are my plugins: aws-deploy br.com.ingenieux beanstalk-maven-plugin 1.2.0-SNAPSHOT accountmarshal-${env} ${env}-${beanstalk.name} ${beanstalk.name}-${env} accountmarshal ${project.artifactId}/${beanstalk.versionLabel}.war verify describe-environments upload-source-bundle create-application-version update-environment aws-deploy-worker br.com.ingenieux beanstalk-maven-plugin 1.2.0-SNAPSHOT accountmarshal-${env} ${beanstalk.name}-${env} Worker accountmarshal ${project.artifactId}/${beanstalk.versionLabel}.war verify describe-environments upload-source-bundle create-application-version update-environmentAnd here is a basic trace of the steps for aws-deploy-worker. As you can [INFO] --- beanstalk-maven-plugin:1.2.0-SNAPSHOT:describe-environments On 13 January 2014 09:18, Aldrin Leal notifications@github.com wrote:
|
|
I'm going to review it. I have some Integration Test in the works and I expect to have you guys something these days. Meanwhile, you can use the -SNAPSHOT for the create-environment tasks, which is a good thing |
|
There's a new build, and you'd need to change from workerEnvironmentName to environmentRef (cnamePrefix is also suggested to be, say, cnameprefix.elasticbeanstalk.com). I'm going to consolidate that in the new IT so it could be easier understood, but if you have the guts to try now, just let me know :) |
|
Thanks Aldrin. I will review and get back to you. On 20 January 2014 17:41, Aldrin Leal notifications@github.com wrote:
|
|
Dominic, Thanks, while I still have some work to do with integration testing, this helped me cover the legacy S3 stuff. I'm not finished, but here's what happens: Basically, I created a new project using the archetype and ported your statements over it, so you could track the diffs and figure it out. Its at this address. Now, lets look at the changes.
So here are the commands I've used so far to test it properly, once I've applied the changes:
In this case, I wanted to update / create an environment
Looks up the latest version and creates a worker. Creates a new version and updates, as expected Updates just the worker to the latest version.
does a zero-downtime-redeploy on Webserver Environment (note this DOES NOT WORK with Worker Instances)
Terminates the WebServer Environment
Same but for the worker instance btw, a build of 1.2.0-SNAPSHOT should be deployed soon enconpassing those scenario |
I have 3 environments running in an application and am using beanstalker to deploy from Jenkins using the same maven profile.
Recently, I changed one environment from a webserver type environment to a worker type environment. I am now receiving an error [environment not found] on the update environment call for the worker type environment:
Is it possible to deploy using update-environment to a worker type environment ?
Do I need to use a different approach for these types of environments ?
The text was updated successfully, but these errors were encountered: