AWS App Runner builder+releaser

[thiskevinwang]

Description

This introduces the aws-apprunner builder & release-manager components

example:

#...
  deploy {
    use "aws-apprunner" {
      name   =  "my-service-name"
      region = var.region
      port   = 8080
      static_environment = {
        "PORT" = "8080"
      }
    }
  }

  release {
    use "aws-apprunner" {
    }
  }
# ...

Screenshots

TODO

• pass Waypoint Labels to App Runner Tags
• waypoint exec will not be supported as you cannot shell into an app runner replica
• static env vars get updated on subsequent waypoint up - 5b7a79d
• document recommended -prune=false, similar to builtin/nomad/canary - 9e75fea

Fixes #1503

[thiskevinwang]

@briancain @paladin-devops 👋 — do you have any guidance for making a component (platform, releaser, etc.) opt out of Waypoint's default pruning behavior?

I'd like to have only waypoint destroy invoke the Destroyer, and have waypoint up not prune older deployments/releases. AppRunner really only keeps track of 1 "service", so there's nothing to prune.

[briancain]

@thiskevinwang - Unfortunately I don't think this is something that's configurable via a plugin. Pruning is handled at the job level and as far as I can think I don't know of a clean way for you to disable it automatically.

[paladin-devops]

@thiskevinwang Brian is right. I faced something similar with the canary plugin for Nomad. In the documentation for the plugin, I advise users to use -prune=false for now though!

[thiskevinwang]

@paladin-devops, ok, sounds good to me! (Though an accidental waypoint up without -prune=false seems very scary 😅 )

[briancain]

@thiskevinwang @paladin-devops - since this has come up a couple of times with plugins, might be worth opening a feature request and we can figure out how to support something like configuring pruning via plugins!

[briancain]

Hey there @thiskevinwang - what's the status on this PR? If there's still work to do, it might make sense to keep your branch active but close this PR to save you the trouble of fixing rebases while it goes stale.

[thiskevinwang]

@briancain I'd say close this, unfortunately. 😢 🥲

As is, the functionality (waypoint up) in this PR works but I've never felt comfortable about... mostly in that it's too easy to auto-destroy your app (a single App Runner service) through Waypoint's default pruning behavior.

[thiskevinwang]

it might make sense to keep your branch active but close this PR to save you the trouble of fixing rebases while it goes stale.

Closing PR this but I'll leave the branch! & FWIW, because this PR is mostly additive, rebases haven't been an issue :)