feat(lambda-function-url): URL releaser component

[thiskevinwang]

Description

This is adds a lambda-function-url plugin (with Releaser component only) that leverages the new Lambda Function URLs.

This approach only releases a function URL for the unpublished Lambda function, and does not leverage URLs for aliases of specific function versions

Note, from AWS:

You can add a function URL only to the unpublished function version, or to an alias. To configure a function URL, go to the unpublished function page, or choose an alias from the Aliases tab.

This leaves the CORs configuration as a TODO for the near future.

Closes #3184

Usage

#...
  release {
    use "lambda-function-url" {
    }
  }
}

Screenshots

Waypoint UI

[briancain]

Looking good Kevin. I know this is still in draft, and it looks like there's some todos, but figured I'd drop a few comments as you work on it. Excited to see this land! 🎉

[briancain]

Overall looks pretty great! Just a few comments and requests from me 👍🏻

[briancain]

Is there an AWS SDK function here we could use instead to validate the creation/existence of a lamba url instead of http.Get?

[thiskevinwang]

I don't think there's a healthcheck-like API for Lambda 🤔. (Makes sense the its ephemeral nature)

• lambda - available commands
• (looking for something like elbv2::describe-target-health)

1. I'm now realizing that AWS_IAM auth type would cause this unsigned http.Get to be return a 503
   Maybe
2. Maybe wait or invoke are viable options...

[briancain]

Does the lambda get-function help at all? I don't know if it has any kind of health or status in the return response. Otherwise yeah maybe the way to go is an http.Get. Might be another good question to ask the team this week and see what they say.

[thiskevinwang]

get-function doesn't return any useful status information. I'll shoot a message to the Waypoint team slack for some opinions!

[thiskevinwang]

@evanphx Moved the releaser into a new plugin folder, and the usage is now as you suggested:

app "blah" {
   release {
      use "lambda-function-url" {
           ....
      }
  }
}

[evanphx]

A couple minor things!

[briancain]

Thank you Kevin!! This looks great ✨

[thiskevinwang]

Hey @evanphx / @briancain belated question:

Is this PR's changes expected to be included in v0.8.x, or will it be available in the next v0.9.x minor line?

I spent an hour or so trying to debug why my remote runner (k8s) was responding with...

! 1 error occurred:
        * plugin "lambda-function-url" not found

...only to realize that this PR's changes weren't in the in the v0.8.2 release

---

Update:

I think I figured out how to update my server & runner with the latest code from main

waypoint server upgrade \
  -auto-approve \
  -k8s-server-image=ghcr.io/hashicorp/waypoint/alpha:02952e297 \
  -k8s-odr-image=ghcr.io/hashicorp/waypoint/alpha-odr:02952e297

[briancain]

@thiskevinwang - looks like this pull request wasn't backported, so it didn't make it into the 0.8.2 release. We can post backport this PR now and it will go out in the next release. Sorry about that!