Constraints when designing plugins

Hello fine folks! So far loving Waypoint - I did, however, have one question that falls more along the lines of “opinion” so I figured I’d ask here.

I have a MERN stack SPA contained in a monorepo, so currently to build the React static files I’m following along with the example here. Suppose I wanted to set that up with a CDN like Netlify or Cloudfront instead, but still wanted to utilize the Waypoint flow.

What I’m considering is building a custom plugin that handles the build and deploy phase for the CDN, and wanted to ensure this is a “kosher” approach using Waypoint. Something along the lines of:

...
app "frontend" {
  path = "frontend"

  build {
    use "yarn" { // custom builder plugin
      script = "build"
      output = "dist" // ends up being frontend/dist
    }
  }

  deploy {
    use "aws-cloudfront" {
      src = "dist"
      ...
    } // custom deploy/release plugin
  }
}
...

While I know this would be possible, I wanted to make sure this is still the intent of the Build / Deploy interfaces. Thanks!

1 Like

Hello! I’m in a similar position as you are… I’m afraid I can’t point you in any direction, but I can atleast bump this for attention :slight_smile:

Did you get anymore info elsewhere?

Nope, since it’s mostly opinion figured I’d just go ahead with what my team and I want to do.

1 Like