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
Not everyone has a deployment pipeline that is glued to GitHub Actions. For use-cases where cdktf-cli is used in other ways, it could be nice to have an action that just installs the cli (locally in the repo and using a cached lockfile) and allowing later commands to invoke it with npx.
Today, the alternative to this is to check in a package.json and lockfile in the repo, and this is a bit strange for people who don't use node otherwise.
References
No response
Help Wanted
I'm interested in contributing a fix myself
Community Note
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
Not everyone has a deployment pipeline that is glued to GitHub Actions. For use-cases where cdktf-cli is used in other ways, it could be nice to have an action that just installs the cli (locally in the repo and using a cached lockfile) and allowing later commands to invoke it with npx.
Today, the alternative to this is to check in a package.json and lockfile in the repo, and this is a bit strange for people who don't use node otherwise.
References
No response
Help Wanted
Community Note