Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
support disabling the agent service #280
We use a Packer workflow to create AMIs for our apps and then promote them through non-production environments before deploying to production. In non-production environments, it is desirable to install the Datadog Agent, but leave the service stopped and disabled via an environment attribute setting. Once in launched in production, the Agent starts and is enabled.
The cookbook already had an attribute to stop the Agent, but not to control the Agent service's
Hi @hydrant25 !
Thanks for taking the time to send this.
I think the idea is sane, but the naming and logical selection seems to be in direct opposite of the other attribute used to control the service behavior.
I'd recommend something similar, like
Can you take a pass at renaming?
@hydrant25 that's awesome, thanks!