feature: RunTrigger gRPC endpoint for Waypoint Server

[briancain]

This pull request introduces the service level function RunTrigger which will queue a job based on an existing stored trigger URL configuration using the ID requested. It also optionally allows for any configuration variable overrides on the request.

I kept the targeted runner to Any until that work is finished. It will be easier once the targeted config is available based on the project and application.

The next step after this is to work on the HTTP handler. It should register a trigger URL id as a valid route, and if a request to that endpoint is called it will take a run trigger request with a registered trigger URL id and call this grpc func (similar to how the HTTP exec works) to queue the job request and optionally stream back the job outputs to the requester.

I tested this endpoint using the waypoint-grpc helper tool in contrib: https://github.com/hashicorp/waypoint/tree/main/contrib/waypoint-grpc

[briancain]

@krantzinator suggested maybe we could introduce a RunTrigger source type here too. Although the CLI type does exactly what we want here, I think.

[catsby]

Looks good so far! I had a few nit-picks and some questions about the copy. Probably no blockers but wanted to ask first

[krantzinator]

Quick comment -- can we make the error message for a missing op type a bit more informative?

! Empty operation type. Operation type must be set with the `-op` flag as one of the following values:
  build, push, deploy, destroy-workspace, destroy-deployment, release, up, init

[krantzinator]

Hm I'm getting some odd screen wrapping behavior when I have multiple triggers:

Looks like this is just in general, as it doesn't do well when the screen isn't wide enough.
Maybe we should present minimal information in the list and only show more in json format or something? And prioritize getting this in the UI as well.

Oh, idea! Maybe list returns just that -- a list of IDs and/or Names. And then leave the detailed version to inspect. This would also be a good use case for filters...

[krantzinator]

These cases should all have operation removed from the sentence (so just build instead of build operation). The column heading is Operation so it's redundant.
https://github.com/hashicorp/waypoint/blob/f564326568b7eff4496aec3ec9b61151d2fd677d/internal/cli/trigger_inspect.go Line 87-111

	case *pb.Trigger_Build:
		opStr = "build operation"

[krantzinator]

Bug: trigger inspect has an id flag but also requires an argument that it uses for <trigger-id>. It should use one or the other. I hit a panic, as you would expect, when I used the flag but did not provide an argument.

[briancain]

@krantzinator - thanks for the feedback!

• I've updated waypoint trigger list to only show a few options by default, and included a -full flag to show everything I was showing before.
• I fixed the panic in the CLI if you specify an id by flag but not argument for the waypoint trigger inspect command.
• Removed the operation text from inspect and list
• Included which flag to set if no operation is set

[krantzinator]

Could you add a note on trigger-specific variables? I want to test it but it's not covered in the docs :)

[krantzinator]

I have more testing I want to do when HTTP hits, but this looks good!

[briancain]

Thank you all who took the time to review and test! Super helpful, appreciate you all ❤️ 🙏🏻

[paladin-devops]

When this is available for HTTP I'd love to try to configure Docker webhooks to use this (to kick off my docker-pull builds)!

[briancain]

Hey there @paladin-devops - soooon! I hope to have a draft PR up this week 😄 Once it's up, it'll likely go out in the next minor Waypoint release. I can give you a ping if you're interested in checking it out in the PR form.

[paladin-devops]

@briancain I spotted your PR, built it locally and it worked like a charm! Working on using something like Smee or Ultrahook to proxy the DockerHub webhook to Waypoint in a private network.

[briancain]

Awesome @paladin-devops !! That's great to hear. Appreciate you trying that PR early. Very pleased to hear it worked like a charm 😄