Klaus
05/21/2022, 1:01 AM.env
file. While all worked as expected for my normal stack, the tags were missing in the DebugStack.
The reason for that is the changed run directory during debug stack initialization, which means the environment isn't behaving as I expected.Jirawat Uttayaya
05/23/2022, 10:28 AMNeil Balcombe
05/23/2022, 1:31 PMIdentityPoolId: auth.cognitoCfnIdentityPool.ref
is not recognised.
I had to change to
IdentityPoolId: auth.cognitoIdentityPoolId ? auth.cognitoIdentityPoolId : "none",
To get it to work correctly.Klaus
05/23/2022, 7:17 PMRudi
05/23/2022, 8:09 PMexport default function main(app) {
app.setDefaultFunctionProps({
runtime: "nodejs16.x",
srcPath: "backend",
bundle: {
format: "esm",
},
})
const storageStack = new StorageStack(app, "storage")
app.stack(storageStack).stack(ApiStack)
}
but now get:
Stacks: Building changes...
Stacks: Synthesizing changes...
TypeError: fn is not a function
at stack (/home/rudi/projects/notes/node_modules/@serverless-stack/resources/src/FunctionalStack.ts:23:19)
at App.stack (/home/rudi/projects/notes/node_modules/@serverless-stack/resources/src/App.ts:389:17)
at Object.main (/home/rudi/projects/notes/stacks/index.js:19:7)
at Object.<anonymous> (/home/rudi/projects/notes/.build/run.js:94:16)
at Module._compile (internal/modules/cjs/loader.js:1063:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
at Module.load (internal/modules/cjs/loader.js:928:32)
at Function.Module._load (internal/modules/cjs/loader.js:769:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
at internal/main/run_main_module.js:17:47
manitej
05/25/2022, 3:12 AMmanitej
05/26/2022, 5:26 PMKlaus
05/27/2022, 12:19 PMp0wl
05/27/2022, 12:24 PMTonny (sstNerd)
05/28/2022, 7:11 AMMischa Spiegelmock
05/28/2022, 8:35 PMMischa Spiegelmock
05/28/2022, 11:15 PMmanitej
05/30/2022, 4:14 PMNeil Balcombe
05/31/2022, 2:51 PMBob Wall
05/31/2022, 4:58 PM// Show the endpoint in the output
stack.addOutputs({
BucketName: bucket.bucketName,
});
Jan Nylund
06/05/2022, 12:04 PMTony J
06/09/2022, 4:12 AMAndrew Brown
06/09/2022, 7:35 PMDevin
06/09/2022, 11:07 PMmickey phoenix
06/13/2022, 9:47 PMserverless.yml
, that it even begins to be clear that it’s about Serverless Framework rather than modern SST.
3. No breadcrumbs or section-based organization for the Archives pages. From a given Archives page, such as the above, there’s no way to tell what section of the guide it’s located under, other than the aforementioned “open up the table of contents and search for the page title”. It would be extremely helpful to have either or both of:
a. Breadcrumbs at the top, like `Archives > Serverless Framework > Building a Serverless API > Add a list all the notes API”.
b. A side nav bar that displays the guide section hierarchy, auto-expanded to the currently open page.
i. Note that the current right-side nav bar does not auto-expand, does not highlight the current page, and shows up on pages (e.g. this one) that are not actually indexed from it at all.
4. Consistent use of “Serverless Stack”/“SST” and “Serverless Framework” language.
a. Section titles like “BUILDING A SERVERLESS API” are actively confusing, when we are dealing with two such similarly named frameworks.
b. Some pages, such as this one, are under really obscure or even misleading sections of the guide. This page is about storing secrets securely using Serverless Framework — but it’s in the “Best Practices” section of the (archived) guide, and nowhere in the section title, the other page titles, or the page itself is “Serverless Framework” explicitly mentioned.
5. The “Search” feature on docs.serverless-stack.com appears to only search the v1 constructs, even if one is currently on a v0 constructs page. This makes the search function effectively useless for those of us who are on v0. I understand that this is a “me problem” — but it would be great if the search function were context-aware, or at least offered the v0 search results (appropriately tagged) rather than suppressing them.
6. It would be great if all of the v0 constructs pages had the same warning at the top that the main “v0 Constructs” has (i.e., “_CAUTION This is the SST v0.x Constructs doc. SST v1 is now released. If you are using v1, see the v1 Constructs doc. If you are looking to upgrade to v1, check out the migration steps._“). It would help people who accidentally ended up in the wrong version to figure out what had happened to them. Without that header, it’s really easy not to notice that the URL has changed from “…constructs/v0/Api” to “…constructs/Api” or vice versa.Mirza
06/15/2022, 5:38 AMnpm install bootstrap react-bootstrap react-icons
These should probably be corrected to include --save/--save-dev in the future?Mirza
06/15/2022, 6:01 AM{
/* Finally, catch all unmatched routes */
}
<Route path="*" element={<NotFound />} />;
The code above makes it look like you are meant to include the curly braces and the "Finally..." comment in your Routes.js file as well which is not the case.Frank
David Shunfenthal
06/16/2022, 7:45 PMlibs/dynamodb-lib.js
file) essentially acting as a DAO. Is this more convenient this way rather than having a standard JS class containing the same methods and a constructor for client
? I’m used to seeing domain-driven interfaces for DAO’s and it feels weird to write an interface for a convenience object like this that I can use in my domain logic, but I definitely want to understand the benefits. Thanks!Mirza
06/17/2022, 12:35 PMimport debug from "../libs/debug-lib";
However, the reference should be to ../util/debug as per page 345
Create a backend/util/debug.js file from your project root with the following
There is a further reference to debug-lib on page 349.
Note that, the handler-lib.js needs to be imported before we import anything else. This is
because the debug-lib.js that it imports needs to initialize AWS SDK logging before it's used
anywhere else.
I think the handler-lib and debug-lib references got cross contaminated from the serverless app instructions from pages 578 and onwards.Mirza
06/19/2022, 11:31 AMT Indie
06/20/2022, 11:09 AMTamás Krasser
06/23/2022, 6:27 AMRodrigo Del Canto
06/23/2022, 6:07 PM