You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 31, 2022. It is now read-only.
Unfortunatelly during the setup phase, OpsWorks deploys all applications
in given stack - there is no way to assign some applications to some
layers only. This parameter resolves this issue (and thus - should be
kept) by filtering supported applications in given layer, to only listed
in it. Notice, that with this option enabled, it won't be possible to
deploy to a given layer an application which is not listed in it.
Resolves#55
dotnofoolin
pushed a commit
to dotnofoolin/opsworks_ruby
that referenced
this issue
Nov 23, 2021
Unfortunatelly during the setup phase, OpsWorks deploys all applications
in given stack - there is no way to assign some applications to some
layers only. This parameter resolves this issue (and thus - should be
kept) by filtering supported applications in given layer, to only listed
in it. Notice, that with this option enabled, it won't be possible to
deploy to a given layer an application which is not listed in it.
Resolvesajgon#55
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Determine somehow currently used layer and included applications in it.
The text was updated successfully, but these errors were encountered: