-
Notifications
You must be signed in to change notification settings - Fork 1
feat: introduce knock init and knock.json file #653
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: introduce knock init and knock.json file #653
Conversation
b80d410 to
6ef4296
Compare
MikeCarbone
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small comment but looks good otherwise, lfg!
mattmikolay
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great! 👏🏻
thomaswhyyou
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few small things, but it's looking good - thanks for taking a stab at this!
99af9b0 to
2e785b9
Compare
2e785b9 to
75788f4
Compare
thomaswhyyou
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking really great- left a couple follow up comments/questions but looks pretty close to ship.
thomaswhyyou
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀🚀🚀

Description
This PR adds project configuration support to the Knock CLI through a
knock.jsonfile. The implementation includes:initcommand that creates aknock.jsonconfiguration file in the current directoryknockDir)This change improves the developer experience by eliminating the need to specify the
--knock-dirflag with every command, allowing for a more streamlined workflow when working with Knock resources.Tasks
KNO-10385