Hi! We’re experiencing a bug in SEED. A deployment got stuck and triggering it manually returns the following error:

{"code":1017,"errorContext":"{}"}

with HTTP status code 500. Retries are getting stuck again (attached screenshot). Please help 😕

hey all @Frank, is it possible to run a CI job after seed has deployed and roll back if that job fails?

Hey seed @Frank. Currently one of my deploy pipelines fails when it reaches the after_deploy hook. The log doesn't even contain an after_deploy hook entry, so I seems to me, that something else must be broken. I have tested the after_deploy hook a two weeks ago or so, but then used the post_deploy phase for executing an e2e test. Today I decided to use the after_deploy hook instead of the post_deploy phase and it doesn't work anymore. I've attached a screenshot of the build log

Deploy part of the build log:

====================
🚀 Deploy
====================
$ cd /tmp/seed/source
INFO: before_deploy hook not found. You can define it in your build spec.
INFO: Learn more about adding a build spec - seed.run/docs/adding-a-build-spec
INFO: Publishing assets...
3.04 s
INFO: Deploying 4 stacks...
34.12 s
❌ dev-notes-StorageStack: dev-notes-Notes already exists in stack arn:aws:cloudformation:us-east-1:168458715623:stack/dev-notes-storage/8c33eb70-33db-11ec-8990-0e40bd8a36fb
➖ dev-notes-ApiStack: Skipped
➖ dev-notes-AuthStack: Skipped
➖ dev-notes-FrontendStack: Skipped
INFO: Stacks output:
Stack dev-notes-StorageStack
Stack dev-notes-ApiStack
Stack dev-notes-AuthStack
Stack dev-notes-FrontendStack

Hello everyone, my app works properly in the local env, but when I try to deploy it via Seed, I get this error. Might someone know what is causing it?

Hi, Is there a way to check if custom webhook I configured for seed.run to push deploy notification to is somehow failing or not?

I am having trouble with Seed.run deploying my Swagger Stack. Its constantly showing the outdated version of the swagger.yml file, while I have tested the app locally and it works as it should. I should probably post this as well here, to show that the Seed.run is actually "building" my swagger before deploying it.

Hi, is it possible to configure seed only to run tests, linting etc on PR stage without running sls deploy command?

Hi, is there a way to update the dotnet sdk to v6? Trying to deploy a dotnet 6 project but I see the build image only supports up to dotnet 5

this is my

package.json

{
  "name": "notes",
  "version": "0.0.0",
  "private": true,
  "scripts": {
    "start": "sst start",
    "build": "sst build",
    "deploy": "sst deploy",
    "remove": "sst remove",
    "console": "sst console",
    "test": "vitest run"
  },
  "devDependencies": {
    "@serverless-stack/cli": "1.2.11",
    "@serverless-stack/resources": "1.2.11",
    "@tsconfig/node16": "^1.0.2",
    "typescript": "^4.7.2",
    "vitest": "^0.12.9"
  },
  "workspaces": [
    "backend"
  ],
  "dependencies": {
    "@aws-cdk/aws-apigatewayv2-authorizers-alpha": "2.24.0",
    "aws-cdk-lib": "2.24.0",
    "aws-sdk": "^2.1145.0",
    "serverless-stack": "^0.1.0",
    "uuid": "^8.3.2"
  }
}

Hi @Frank is there an example of the serverless.yml for https://seed.run/docs/adding-a-service ?

Thank you so much for creating these amazing products! Recently I just ran into a problem with deploying a Next.js site with seed. I followed this instruction to init a next.js site in the

frontend

folder, and this instruction to add the before_build hook. However, the seed complains that it cannot find the

frontend

folder. And this is what I got when I run

ls

as the before_build hook, there is no frontend folder there… Could someone pls help me with this?

I am getting the already exists error when I moved an app from running locally using npx sst deploy to running the same deploy in seed. Seems like an issue if I/users can't move to seed without deleting their cloudfront distribution and dynamodb tables, or am I doing something wrong?

INFO: Deploying 4 stacks...
48.52 s
❌ dev-the-coach-essentials-dynamodb-stack: /dev/mproveData already exists in stack arn:aws:cloudformation:us-east-2:811320874249:stack/dev-tce-dynamodb-stack/12c9fec0-e676-11ec-8106-0a607fc8eac0
✅ dev-the-coach-essentials-s3-stack: Deployed
➖ dev-the-coach-essentials-api: Skipped
❌ dev-the-coach-essentials-site-stack: /dev/siteurl already exists in stack arn:aws:cloudformation:us-east-2:811320874249:stack/dev-tce-site-stack/3d8c6950-e67f-11ec-be6e-065a8584e8c0

hey all — using prisma+seed and having trouble including the

schema.prisma

in the .zip package generated we’re using

packages.individually=true

,

packages.pattern=./schema.prisma

. Using those, the output is like:

lambda.zip

expanded: • schema.prisma • subfolder/ ◦ sub subfolder/ ▪︎ index.js ▪︎ index.js.map and I get an error that

schema.prisma

isn’t found in

sub subfolder

. any way to include that

schema.prisma

file down there/does anyone know what the best way to include

.prisma

files is here? we’re using

serverless-esbuild

+ seed

I have an odd issue… Deploying to

stage

environment via Seed, everything works. In

package.json

, I have these plugins listed in `devDependencies`:

"devDependencies": {
    ...
    "serverless": "3.19.0",
    "serverless-plugin-datadog": "5.1.1",
    "serverless-plugin-git-variables": "^5.2.0",
    "serverless-webpack": "^5.7.1",
    ...
  }

In `serverless.yml`:

service: my-service-name
frameworkVersion: '3.19.0'

plugins:
  - serverless-plugin-datadog
  - serverless-plugin-git-variables
  - serverless-webpack

When deploying to

Prod

environment, I get this error:

Environment: linux, node 14.18.1, framework 3.19.0, plugin 6.2.2, SDK 4.3.2
Docs:        <http://docs.serverless.com|docs.serverless.com>
Support:     <http://forum.serverless.com|forum.serverless.com>
Bugs:        <http://github.com/serverless/serverless/issues|github.com/serverless/serverless/issues>
Error:
Serverless plugin "serverless-plugin-datadog" not found. Make sure it's installed and listed in the "plugins" section of your serverless config file. Run "serverless plugin install -n serverless-plugin-datadog" to install it.
ERROR: Failed to run: SLS_DEBUG=* serverless package --stage prod --package sls-package-output

Using build image “General Purpose 4.0”.

Using a freshly scaffolded SST app with seed I get

error constructs@10.1.31: The engine "node" is incompatible with this module. Expected version ">= 14.17.0". Got "14.15.4" error Found incompatible module.

Does Seed.run rollback feature use code stored on S3?

Is there a way to turn off build notifications for per PR deploys. Our per PR deploys base their settings off our dev stage. and we want notifications for the dev stage

Hi, from this seed’s doc(https://seed.run/docs/adding-a-build-spec.html#build-steps), it says the

node_modules

will be restored automatically in

after_deploy

, but it seems not. I still need to run

yarn install

and it takes almost 2 mins to finish every time. Is that because I missed any setup?

Is there a way to trigger a new deployment in Seed in response to an incoming webhook? In my stack I use the

NextjsSite

to generate a static site using content from a headless CMS. I’m hoping to automate my deploys so that whenever content creators make changes in the CMS, a webhook is sent to Seed, to redeploy the stack with the latest content

Hi, I’ve got a new SST app and the initial seed builds are failing with this error

$ npx sst build --stage dev --verbose
file:///tmp/seed/source/node_modules/@serverless-stack/core/dist/pothos/generate.js:5
import { printSchema, lexicographicSortSchema } from "graphql";
         ^^^^^^^^^^^
SyntaxError: Named export 'printSchema' not found. The requested module 'graphql' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:
import pkg from 'graphql';
const { printSchema, lexicographicSortSchema } = pkg;
    at ModuleJob._instantiate (internal/modules/esm/module_job.js:104:21)
    at async ModuleJob.run (internal/modules/esm/module_job.js:149:5)
    at async Loader.import (internal/modules/esm/loader.js:166:24)
    at async Object.loadESM (internal/process/esm_loader.js:68:5)
ERROR: There was an error synthesizing your app.

Hi, I added a new app to SEED and setup the deployment following the guide. However I am getting a deployment error

error constructs@10.1.27: The engine "node" is incompatible with this module. Expected version ">= 14.17.0". Got "14.15.4" error Found incompatible module.

This seems to be a problem with the enviroment running on seed, how can I fix this?

I should mention there’s nothing special about the “about” page that the error mentions. It’s seemingly random which page fails, sometimes it’s the 404 page. None of my pages have anything interesting to render, there are no SSG or ISR pages.

👋 Any tips or ideas how I can speed up my seed deploys for "noop" commits? Looking at our pipeline breakdown we have the following for a commit that doesn't change any lambda or infra code: 1. Restoring dep cache: 12s 2. Install deps: 3s 3. Build: 38s 4. Publishing assets: 80s 5. Deploy: 19s Bringing the total time to around 3 minutes (I skipped a few smaller steps). It seems like the publishing assets step is taking unreasonably long time compared to everything else. Looking into the step logs I see a lot of

no changes

+

checking if we can skip deploy

and then

skipping deployment

. Any way to speed this up?

hey does anyone know if seed is running any promo codes? Im updating my plan shortly 🙂

Hi! I was just wondering if there were any plans to add some kind of notes/tags support to SEED? I'd like to be able to store some extra information in the stage about IDs, etc, and maybe descriptions about what it should be used for, etc.

Just popping in here to say our team just bumped up to a paid seed plan, can't recommend it enough to others. Whole process with SST/Seed has just been great. 👍

hello i use seed.run actively to deploy my serverless stacks to AWS. it works fine for lat 4 month...Suddenly starting from today when i push anything in github , the build is failing with the following error

[12:53 PM] $ cd /tmp/seed/source
INFO: before_build hook not found. You can define it in your build spec.
INFO: Learn more about adding a build spec - seed.run/docs/adding-a-build-spec
$ cd /tmp/seed/source/serverless-cloudprotect365-complete

$ npx sst build --stage dev --verbose

29.71 s

====================
🚀 Deploy
====================

$ cd /tmp/seed/source
INFO: before_deploy hook not found. You can define it in your build spec.
INFO: Learn more about adding a build spec - seed.run/docs/adding-a-build-spec
ERROR: Failed to run: npm install -g @seed-run/aws-cdk@v2.24.0-seed.1

BRANCH triggers are not working? Just merged into

prod

branch but seed didn’t trigger. This worked last time for me 1 week ago.

Hey, Is there any plan on the roadmap to deploy graviton lambdas via seed.run? I couldn’t find it in documentation.