aws / aws/aws-codedeploy-agent

Add the CodeDeploy agent to the PATH

Aperta
#385 1 commento 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
Rust
Stelle
337
Fork
195
Merge medio
10h 54m
PR unite (30g)
4

Descrizione

> The title only describes one problem. In this issue, I'm reporting several issues.

I've used the instructions [here](https://docs.aws.amazon.com/codedeploy/latest/userguide/codedeploy-agent-operations-install-ubuntu.html) to install the CodeDeploy agent.

(I know this is not the recommended way, but using the AWS System Manager seems more complicated. It's not just one click. You need to associate your EC2 with the AWS System Manager and do other stuff. To me, this looks already too complicated, so I don't even know why this is the recommended way.)

On Ubuntu, it seems that the agent is installed in `/opt/codedeploy-agent/bin/codedeploy-agent`. However, if we do `codedeploy-agent --version` we get a `codedeploy-agent: command not found`, which means we can't directly interact with the agent by just specifying the name, but we need to specify the full path, which is tedious.

Is there any reason why we wouldn't want to add the agent to the PATH? I think the only possible reason not to do this is that, if we decide to remove the agent, we may want to update the PATH. But can't this be done consistently?

The other problem is that `/opt/codedeploy-agent/bin/codedeploy-agent --version` does not return anything because there's no `--version` option, which is so weird. It seems that there are only the options to start, stop, etc., the agent/service. I think there could be other options, like ways to flush the logs, clean up old deployments, self-update the agent and also to remove the agent. Btw, why isn't there already a way to install the agent with `apt` or `apt-get`?

Another problem with CodeDeploy is that there's no way (apparently) to ignore errors in hooks in the `appspec.yml`. I really don't understand why this option doesn't at least exist for the `ApplicationStop` hook, which always fails the first time you're setting a new project. It's so tedious to always have to manual deploy until you get it right. I basically had to do this like 30 times so far because `ApplicationStop` sometimes fails because of what I've just said.

I've just started to use AWS CodeDeploy, but honestly I was expecting it to be more advanced and simpler to use. It looks unnecessary complicated mostly because it lacks many useful features (e.g. I should just need to do `sudo apt install codedeploy-agent` to install it, and after that I should be able to do `codedeploy-agent --version`).

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

Iniziate dalle istruzioni per l’installazione di Ubuntu e dall’entry point dell’agente in /opt/codedeploy-agent/bin/codedeploy-agent, quindi separate le richieste relative a PATH, --version, all’installazione dei pacchetti e agli errori degli hook di AppSpec in ambiti distinti. Verificate il comportamento dei comandi di servizio esistenti e di appspec.yml; done deve essere definito separatamente per una funzionalità selezionata, concordandone il comportamento e la validazione prima dell’implementazione.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
aws, ubuntu
Ambito
cloud, devops
Tipo di issue
Funzionalità
Difficoltà
5/5
Tempo stimato
Più di una settimana
Stato di attività
Ferma
Chiarezza
Da chiarire
Idoneità per principianti
15/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.