localstack
feature request: support ctx.stash for JS pipeline resolver
Is there an existing issue for this?
- [X] I have searched the existing issues
Feature description
Just like VTL, pipeline resolver on JS runtime also have ctx.stash to pass any variable across the entire pipeline.
Currently, localstack returns empty object on ctx.stash regardless of what kind of values were stored.
Pipeline #1
export function request(ctx) {
ctx.stash.example='example'
return {};
}
export function response(ctx) {
return ctx.prev.result;
}
Pipeline #2
export function request(ctx) {
const { example } = ctx.stash; // expect to get 'example'. currently undefined
return { payload: { example } };
}
export function response(ctx) {
return ctx.result;
}
🧑💻 Implementation
No response
Anything else?
No response
Welcome to LocalStack! Thanks for reporting your first issue and our team will be working towards fixing the issue for you or reach out for more background information. We recommend joining our Slack Community for real-time help and drop a message to LocalStack Pro Support if you are a Pro user! If you are willing to contribute towards fixing this issue, please have a look at our contributing guidelines and our contributing guide.
Hello 👋! It looks like this issue hasn’t been active in longer than five months. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.
Hello 👋! It looks like this issue hasn’t been active in longer than five months. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.