1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Although it still seems like there is conflict between .ebextensions and the env.yaml file, I was able to successfully deploy separate .ebextensions folders to their respective environments. I did not need to change my folder structure.
By terminating the instance and allowing my Auto Scaling Group (ASG) to spin up a new instance, I was able to remove whatever bad cache was being used to build the original EC2 instance. Now, my separate environments update in relation to the config files from their respective .ebextensions folder.
répondu il y a 4 ans
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a 2 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 3 mois
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 8 mois