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
Most users will not be using AWS to run beep (or if I am wrong here please correct). The AWS code is mixed in with beep, between the various required configs, extra tests, and extra submodules, there is a clear conceptual separation of beep and AWS deployment but no such separation is reflected in the code; it's all mixed together.
Solution
Move the AWS specific stuff to another repo (e.g., a private deployment repo). Make specific beep versions requirements of the deployment repo
The text was updated successfully, but these errors were encountered:
@ardunn Yeah, this is a good point. I am acutally in the process of removing a bunch of the AWS stuff since we are transitioning away from those tools. Hopefully that should clear up the problems you are seeing here.
Problem
Most users will not be using AWS to run beep (or if I am wrong here please correct). The AWS code is mixed in with beep, between the various required configs, extra tests, and extra submodules, there is a clear conceptual separation of beep and AWS deployment but no such separation is reflected in the code; it's all mixed together.
Solution
Move the AWS specific stuff to another repo (e.g., a private deployment repo). Make specific beep versions requirements of the deployment repo
The text was updated successfully, but these errors were encountered: