While getting a new plugin initially configured, I would use the UI to
begin with, yes.
Your `ls` command starts with 'gocd-' so is filtering out plugins that
don't start with the same (such as the docker elastic agent plugin). If the
version and list of plugins is correct on the admin > plugins
The default go-server docker image is Alpine based, so the equivalent image
would be https://hub.docker.com/r/gocd/gocd-agent-alpine-3.18
Having said this, most folks find they end up building their own agent
image using a GoCD official image as base image, so they can add on
required tooling of
The pluginId in that cluster profile fragment refers to a completely
different ec2 elastic agent plugin so not sure what you're trying to show
us there
Personally, I don't think it's a good idea to be directly configuring
cruise-config.xml especially for plugin-oriented config, since it
Thank you Sriram.
My comments inline please.
Are you planning to run the go server as an ECS instance and The go agent
as a ECS instance?
Satya] Yes, server will be part of ECS (ECS instance) and it will launch
the agents dynamically when theres a job to perform and once the job is
done the agent
