1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
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.
beantwortet vor 4 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr