Re: [go-cd] Elastic agents plugin usage

It seems you are using the third party EC2 Elastic Agent Plugin . This plugin does not implement the plugin API correctly and does not support environments correctly,

Re: [go-cd] Elastic agents plugin usage

Thank you Sriram. Please find my comments below. >Do the various jobs have an elastic profile ID set? Yes, I have two environments staging and prod, so we have separate profiles set for them. Here is pretty much what each profile has: 1. ec2_ami 2. ec2_instance_profile 3. ec2_subnets

Re: [go-cd] Elastic agents plugin usage

Can you be specific about the type of elastic agents you are creating and the plugin you are using. Kubernetes? Docker? Something else? There are many elastic agent plugins. > Here's where it gets tricky: when the staging job completes and triggers > the production job, I expect one of the

Re: [go-cd] Elastic agents plugin usage

On Thu, Apr 25, 2024 at 10:01 PM Satya Elipe wrote: > Hi All > > I'm encountering some issues with the way Elastic agents are launched, > assigned, and terminated. Despite setting the maximum agent count to two, > both agents launch sequentially, with only the first being assigned to the > job.

[go-cd] Elastic agents plugin usage

Hi All I'm encountering some issues with the way Elastic agents are launched, assigned, and terminated. Despite setting the maximum agent count to two, both agents launch sequentially, with only the first being assigned to the job. Here's where it gets tricky: when the staging job completes and