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
Currently targets to deploy during create_gitops_prs run must be built just before the create_gitops_prs execution. This could be error prone and cause deploying of stale versions if targets parameter to create_gitops_prs is not synchronized exactly with targets to build.
Also, there is currently impossible to investigate dependency tree of the deployment using bazel query.
It would be useful to extract the initial step of targets discovery into a gazelle-like generator that would generate a target like this:
# This is the 1st commit message:
app name first
# This is the commit message nazzzzz#2:
clean up file
# This is the commit message nazzzzz#3:
fix reference to proto package
# This is the commit message fasterci#4:
better parse
# This is the commit message fasterci#5:
fix again
# This is the commit message fasterci#6:
fix again
# This is the commit message fasterci#7:
fix again
# This is the commit message fasterci#8:
fix again
# This is the commit message fasterci#9:
fix again
# This is the commit message fasterci#10:
fix again
# This is the commit message fasterci#11:
add debug statements for seeing if branch is dirty
# This is the commit message fasterci#12:
fix again
# This is the commit message fasterci#13:
fix again
# This is the commit message fasterci#14:
fix again
# This is the commit message fasterci#15:
fix again
# This is the commit message fasterci#16:
fix again
# This is the commit message fasterci#17:
fix again
# This is the commit message fasterci#18:
fix again
# This is the commit message fasterci#19:
fix again
# This is the commit message fasterci#20:
fix again
# This is the commit message fasterci#21:
fix again
# This is the commit message fasterci#22:
fix again
# This is the commit message fasterci#23:
fix again
Currently targets to deploy during create_gitops_prs run must be built just before the create_gitops_prs execution. This could be error prone and cause deploying of stale versions if targets parameter to create_gitops_prs is not synchronized exactly with targets to build.
Also, there is currently impossible to investigate dependency tree of the deployment using
bazel query
.It would be useful to extract the initial step of targets discovery into a gazelle-like generator that would generate a target like this:
running such target would be equivalent of building all dependencies and running create_gitops_prs on them.
The text was updated successfully, but these errors were encountered: