David Gray

For reference - this is how we get around this issue - at least for start-api. https://github.com/dacgray/sam-local-start-api-container-image-volume-mount

For me this worked.: ``` function localStorageProvider() { // When initializing, we restore the data from `localStorage` into a map. const map = new Map( JSON.parse(localStorage.getItem('app-cache') || '[]') ) //...

We use MSW for image requests: ```js export const XSSnapshot: Story = { parameters: { cookie: {}, viewport: { defaultViewport: 'xs', }, msw: { handlers: [ rest.get('**/*.svg', async (req, res,...

For reference - this is how we get around this issue: https://github.com/dacgray/sam-local-start-api-container-image-volume-mount

Very difficult - I pieced the current list together from multiple sources and filled in a few blanks myself. Check if you can use the newer SP-API if you're not...

Apologies - another non-answer: We abandoned using XSDs - instead using https://developer.amazonservices.com/tools, generating inventory spreadsheets and manually uploading, and later using SP-API where possible. If you're figuring out how to...

After more experimenting, this pattern seems to work: ``` tags = [ "Env=prod", "Repo=shop-restack", "Stack=shop-restack-ecs-stack", "Cost Group=Restack" ] ```

On second thought, best to keep this open since behaviour is not as expected.

That sounds about right.