Closed toVersus closed 1 year ago
Hey @toVersus thanks for filing this issue! It makes sense to me to have this command. I think this would be useful also when we are generating projects at runtime or as you mentioned having alot of projects in digger.yml
Please go ahead and create the pull requests for review 👍
Thanks! I submitted the PRs to implement this feature.
hey @toVersus thanks so much for the contribution - Would you be interested in further contributing to digger? We have a few issues that could use your help - if you are interested to discuss could you message me on slack please?
Thank you !!
https://join.slack.com/t/diggertalk/shared_invite/zt-1tocl4w0x-E3RkpPiK7zQkehl8O78g8Q
It would be great to have a
digger show-projects
command to show all the impacted projects by the PR on the comment, and use that info to run other commands likedigger plan -p <project_name>
ordigger apply -p <project_name>
without looking at the digger.yaml file. We currently define a lot of projects in the digger.yaml file and cannot remember the relationship betweendir
andname
of the project.Something like this
digger.yaml:
GitHub comment output:
If this feature request is acceptable, I will send the PR do the implementation. (WIP: https://github.com/toVersus/digger-lib-orchestrator/commit/10387e241c7c7ff28f4075b865c4c26229758120, https://github.com/toVersus/digger/commit/bf59142c84267f6b1a42efeeb357347d58d80245)