Open jarrettandrulis opened 2 years ago
Marking this as low priority. I'm hesitant to implement this because it loses some of the explicitness that rdk deploy
currently has. If you're in the wrong directory by accident and run rdk deploy
, you could make unintended changes. Requiring additional context at the command line may be helpful at preventing misconfiguration.
Let me know if I'm understanding this right.
If I am in the rule folder
bucket_not_public
, then you would likerdk deploy
to deploy the contents ofbucket_not_public
instead of having to change directory to the parent and then specifyingrdk deploy bucket_not_public
?