Love the inactive settings for reducing instances on the inactive stack.
I was wondering if commands or container commands could be executed when the configuration values are updated/set for the inactive settings?
My specific use case would be to turn off sidekiq on the inactive stack via shell script (in case jobs are updated and the inactive stack would be servicing sidekiq jobs with out of date code)
Ebs docs say commands are executed at each deployment and environment update but I'd need to run a specific command at the inactive transition rather than the same one run at deployment. My initial attempts returned "can't do that here" errors of various types
Love the inactive settings for reducing instances on the inactive stack.
I was wondering if commands or container commands could be executed when the configuration values are updated/set for the inactive settings?
My specific use case would be to turn off sidekiq on the inactive stack via shell script (in case jobs are updated and the inactive stack would be servicing sidekiq jobs with out of date code)
Ebs docs say commands are executed at each deployment and environment update but I'd need to run a specific command at the inactive transition rather than the same one run at deployment. My initial attempts returned "can't do that here" errors of various types