Terraform lockfiles were magically pulled in with a pathglob. This meant that --changed-since had no visibility on changes in the lockfile. This MR adds a synthetic target for terraform lockfiles, wires it into dep inference, and uses its Sources to pull it in.
The key reason to use a synthetic target instead of a normal target with tailor is that the lockfile must be called .terraform.lock.hcl and must be in the same directory as the root module of a Terraform deployment. So any such file must be a Terraform lockfile, and no other file can be.
Terraform lockfiles were magically pulled in with a pathglob. This meant that
--changed-sincehad no visibility on changes in the lockfile. This MR adds a synthetic target for terraform lockfiles, wires it into dep inference, and uses its Sources to pull it in.The key reason to use a synthetic target instead of a normal target with tailor is that the lockfile must be called
.terraform.lock.hcland must be in the same directory as the root module of a Terraform deployment. So any such file must be a Terraform lockfile, and no other file can be.closes #14790