I know I can put commands in my source code in .ebextensions/*.config using the commands
array. These are executed on every deploy however. What about if I want to execute a configuration command only once when spinning up a new instance?
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试):
问题:
回答1:
Commands can be run conditionally using the test:
modifier. You specify a test to be done. If the test returns 0, the command is run, otherwise it is not.
If the last command in your config file touches a file, and the commands above that you only want to run once check for the existence of that file, then those commands will only run the first time.
commands:
01-do-always:
command: run_my_script
02-do-on-boot:
command: script_to_run_once
test: test ! -f .semaphore
99-signal-startup-complete:
command: touch .semaphore
On Windows it would be something like this
commands:
01-do-always:
command: run_my_script
02-do-on-boot:
command: script_to_run_once
test: if exists c:\\path\\to\\semaphore.txt (exit 0) else (exit 1)
99-signal-startup-complete:
command: date > c:\\path\\to\\semaphore.txt
回答2:
On Windows this should work:
commands:
01-do-always:
command: run_my_script
02-do-on-boot:
command: script_to_run_once
test: cmd /c "if exist c:\\semaphore.txt (exit 1) else (exit 0)"
99-signal-startup-complete:
command: echo %date% %time% > c:\\semaphore.txt
Note that I had to change the test
command from Jim Flanagan's answer.