Missing Steps for imaging purposes
Closed this issue · 5 comments
Hello Guys ,
Thanks you for your alert logic agent role , I am facing an issue using it maybe you can tell me if I did something wrong or not.
We have a tool that build our AMI (launch an instance , apply role , stop the instance, create the AMI) using ansible and then we launched those AMI in a cloudformation template.
Once you apply the imaging flag, the provisionning is not called at all
So once our instances starts the application is not provisionned at all , I don't think this is the right behavior.
I have created a PR : #7
Can you correct me if something is wrong here ?
@blade2005 ok so should I do those change on my fork and update my PR or should I leave it to you ?
Also there one flag I don't know his purpose the flag al_agent_for_autoscaling because if I read well the install docs when we do AMI based we need to provision using this command
/etc/init.d/al-agent provision --key <UNIQUEREGISTRATIONKEY> --inst-type host
So for me al_agent_for_autoscaling and al_agent_for_imaging both need the option :
--inst-type host
Am I wrong ?
Ok I will try to do that ,
I was following the instruction of this pdf
ESS-Unified Agent Deployment Guide.pdf
Should I trust this file or this url :
https://docs.alertlogic.com/install/alert-logic-agent-linux.htm
Ok I will reach them , thanks for your help .
Let me know when I/You can merge the PR
Nope It didn't work , I couldn't find an easy and clean way of doing it so right now duplicate the line if the safest choice
@blade2005 Thank you