- Newest
- Most votes
- Most comments
Hi tuxan,
Thanks for reaching out.
-
From the stack trace on
eb init
, it appears thateb
is waiting for user input. Passing the--platform
toeb init
should get you around that problem. -
Note that there is no problem with your
eb clone ...
command per se, however, it is good practice to short-circuit command combinations using&&
(i.e. --eb init ...
&&eb use ...
&&eb clone ...
), so that the first command that fails is the last to execute.
Please let me know if you encounter further problems.
Thanks,
Rahul.
Thank you Rahul.
Yes, I went with the short-circuited command combinations. Thought explicitly laying them out will make for clearer reading up here.
I ended up resolving the issue by creating a new directory for each environment and cloning from within the directory. After the clone I took out the directory and moved on to the next environment. Lots of IO... but just about all I could think of to get passed the problem.
It appeared that there was a lot of conflict/contention making use of the same .elasticbeanstalk/config.yml file in a single directory for all the environments being cloned and making use of different directories resolved it.
Thanks for your response.
Cheers.
Relevant content
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 4 months ago