sst / console Goto Github PK

there's only 2 functions (plus a NextjsSite), and both of them are python functions. As you see in the screenshot, it shows a bunch of duplicates of one of the functions, and reports all of them as js.

I checked if it maybe reports one per function version, but there's only one version available of that one

With the release of Ion I have transitioned my applications to run on Cloudflare workers. It would be great if the console supported the Cloudflare console. Is this functionality planned, and is there a timeline?

It would be super handy to have multi-select toggle on the stages for a given alert. We have ~25 (and growing) stages and it would be super painful to set up these alerts each for all of them. Selecting all doesn't work for our use case as there's ~1-2 that we want to treat differently.

I just tried to set up auto-deployment, and the repo dropdown list didn't show a newer repo that I created a few days ago, despite having given access to all repos (I think).

It still didn't show up after I toggled the GitHub integration off and on again (and gave access again on the GitHub site).

The only way I got the new repo to show was to delete the whole console GitHub app and have that reinstall when I turned the GitHub integration on again on the SST console site.

I validated this again by creating another new repo now and it didn't show up when I tried to link it to an existing console app.

I've encountered a console crash in the "local" tab with the following error:

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'handler')
    at get children (index.c1f2b17c.js:275:89501)
    at Array.uN (index.c1f2b17c.js:1:9105)
    at Array.uN (index.c1f2b17c.js:1:9105)
    at Object.fn (index.c1f2b17c.js:1:16341)
    at rN (index.c1f2b17c.js:1:5243)
    at Bu (index.c1f2b17c.js:1:5184)
    at $t (index.c1f2b17c.js:1:1476)
    at Ne (index.c1f2b17c.js:1:16316)
    at Object.fn (index.c1f2b17c.js:1:21342)
    at rN (index.c1f2b17c.js:1:5243)

This error occurs at these lines:

get children() {
   return e.mixed ? e.function.handler : e.invocation.errors[0]?.message || e.invocation.logs[0]?.message
}

I encounter this error when starting the execution of a state machine. It's a rather simple state machine that triggers only one Lambda function.

I've noted that my Lambda function does not appear in the resources tab, and I suspect the error is related to this issue.

For your information, this works correctly on the old console.

I would like to add the following details about my stack:

    const notifyStatistics = new Function(stack, 'gaming-notify-statistics', {
        handler: 'packages/_gaming/steps/notifyStatistics',
        environment: {
            ...commonEnvironment,
            ...gamingEnvironment,
            GAMING_API_URL: graphApi.url,
        },
        permissions: [
            ...gamingPermissions,
            new cdk.aws_iam.PolicyStatement({
                actions: ['appsync:GraphQL'],
                effect: cdk.aws_iam.Effect.ALLOW,
                resources: [graphApi.apiArn + '/*'],
            }),
        ],
    })

    const notifyStatisticsStateMachine = new StateMachine(
        stack,
        `${app.stage}-${app.name}-gaming-notify-statistics-state-machine`,
        {
            definitionBody: DefinitionBody.fromChainable(
                new LambdaInvoke(stack, 'NotifyStatisticsTask', {
                    lambdaFunction: notifyStatistics,
                }),
            ),
        },
    )

db:push is failing. need to downgrade drizzle-kit to 0.19.5 (that worked for me)

planetscale/discussion#497

I wanted to work to see if I could work on #7 but when I tried to run the project locally pnpm dev I realized there's a lot of DNS dependencies in the stacks. It would be cool if these could be disabled so I could spin the project up locally easily so that I can play around with contributing. Not sure if there's a better way to do that now.

Our AWS Org settings require all new IAM roles to have a specific Permission Boundary applied. Any role create command where the role does not have this permission boundary will fail.

I have followed the instructions to set up the Console, and when I deployed the console stack in us-east-1, I customized the template so that the SST role you're using has the Permission Boundary.

BUT since you are using that role to create other roles, they also need the same permission boundary applied. Is there a way I can instruct SST Console to use a certain boundary for any roles that it wants to create?

See related discord thread: https://discord.com/channels/983865673656705025/990989982799900792/1241145612624330872

when I type the first number in the input the page refreshes with with ?error=invalid_code in the query params, below is the video showing this behavior

I'm trying to clean up after having made a bunch of different stacks to test various junk. There is one stack left that I'm not able to delete:

I assume that all the resources are actually deleted because this page doesn't seem to load any resources while others do.

I'm running the following command:

➜  sst remove --stage prod
SST ❍ ion 0.0.386  ready!

➜  App:        remix-redirect-issue
   Stage:      prod


×  Stage not found

There's a slight rendering issue in the list of resources that have logs. The name of the function isn't showing so the link isn't clickable. Inspecting the element shows the link is there but the element is just hidden because the name hasn't rendered, leaving an empty anchor tag.

Offending LOC

So I've updated my payment preferences to make sure there are no billing issues, but I'm getting these errors on the deployed Console stack on us-east-1 N. Virginia.

Nothing here is clickable.

I haven't created any app stacks which may be required for the Console stack to be created.

So I don't really know where to go from here.

We have been using Autodeploy on our project.

We have a Turborepo monorepo, and we import some shared config from a local package in our sst.config.ts

With this approach the Autodeploy service is not able to read our sst config and the deploy fails, we see Error evaluating sst.config.ts

Once we replace the shared config with actual values the deploy works great.

Let me know if you need a reproducible example, or if i've raised this in the right place.

• Ryan https://discord.com/channels/983865673656705025/990989982799900792/1260943846183931944

Problem was initially submitted in following issue

It still persists, just came back to autodeploy run again and found error as such:

19:11:36.498
HEAD is now at 918c50f ci: updated test db instance
19:11:36.498
Running: npm install -g [email protected]
19:11:37.654
npm ERR! code ETARGET
19:11:37.654
npm ERR! notarget No matching version found for [email protected].
19:11:37.654
npm ERR! notarget In most cases you or one of your dependencies are requesting
19:11:37.654
npm ERR! notarget a package version that doesn't exist.
19:11:37.654
npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-08-05T17_11_35_625Z-debug-0.log
19:11:37.654
Error: Failed to run: npm install -g [email protected]
19:11:37.654
at shell (file:///tmp/buildspec/index.mjs:242:13)
19:11:37.654
at install (file:///tmp/buildspec/index.mjs:172:9)
19:11:37.654
at workflow (file:///tmp/buildspec/index.mjs:159:9)
19:11:37.654
at runWorkflow (file:///tmp/buildspec/index.mjs:164:11)
19:11:37.654
at handler (file:///tmp/buildspec/index.mjs:48:11)
19:11:37.654
at async file:///tmp/buildspec/[eval1]:1:122
It is caused by yarn having two releases - classic which is on npm as versions 1.2.x and latest yarn which is a bit disconnected from yarn classic and installed through corepack which is shipped with npm. More about how to install latest yarn here: https://yarnpkg.com/getting-started/install

I think it would be the best to support this feature by using corepack.

We have been trying out Autodeploy for PR deploys.

The PR deploy works great, but when we close the PR the job starts again, which we assume is to remove the ephemeral environment.

When this happens, the job fails with:

ReferenceError: binary is not defined
--
109 | at remove (file:///tmp/buildspec/index.mjs:208:14)
110 | at workflow (file:///tmp/buildspec/index.mjs:161:48)
111 | at async runWorkflow (file:///tmp/buildspec/index.mjs:164:5)
112 | at async handler (file:///tmp/buildspec/index.mjs:48:5)
113 | at async file:///tmp/buildspec/[eval1]:1:122
114 | [sst.deploy.end]

This is from the codebuild logs and happens right after Running: pnpm install --frozen-lockfile has succeeded.

Let me know if this is enough information, or if i need to provide a repo with a reproducible example.

Thanks!

When running autodeploy on repo configured to use yarn berry (package has key packageManager set to [email protected] i receive

12:53:36.146
�[0;32mSuccessfully added �[38;2;255;140;0mSST ❍ ion �[0;32mto $PATH in /root/.bashrc�[0m
12:53:36.146
Running: yarn install
12:53:36.715
error This project's package.json defines "packageManager": "[email protected]". However the current global version of Yarn is 1.22.22.
12:53:36.715
Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19.
12:53:36.715
Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.
12:53:36.715
Error: Failed to run: yarn install
12:53:36.715
    at shell (file:///tmp/buildspec/index.mjs:229:13)
12:53:36.715
    at install (file:///tmp/buildspec/index.mjs:169:37)
12:53:36.715
    at workflow (file:///tmp/buildspec/index.mjs:159:9)
12:53:36.715
    at runWorkflow (file:///tmp/buildspec/index.mjs:163:11)
12:53:36.715
    at handler (file:///tmp/buildspec/index.mjs:44:11)
12:53:36.715
    at async file:///tmp/buildspec/[eval1]:1:122

Expected behavior:
Console should run corepack enable so that corepack can resolve package manager version correctly.