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
In some of our staging environments we don't have ES hooked up, and it's controlled by an environment variable to set all strategies to :bypass in an initializer. However when you fire up a console in that environment, an instance of the :urgent strategy gets added to the stack:
Is there a way to avoid this :urgent strategy getting added?
Also, ideally I'd love to not have to worry about strategies at all when I just need to completely disable Chewy in certain environments. I'd love for there to be a configuration object like enabled that could be set to true just to stop everything Chewy related.
The text was updated successfully, but these errors were encountered:
In some of our staging environments we don't have ES hooked up, and it's controlled by an environment variable to set all strategies to
:bypass
in an initializer. However when you fire up a console in that environment, an instance of the:urgent
strategy gets added to the stack:Is there a way to avoid this
:urgent
strategy getting added?Also, ideally I'd love to not have to worry about strategies at all when I just need to completely disable Chewy in certain environments. I'd love for there to be a configuration object like
enabled
that could be set to true just to stop everything Chewy related.The text was updated successfully, but these errors were encountered: