Is there a way to get SST outputs as post deploy environment variables? And/or use SST’s

--outputs-file

? (I might well be missing something obvious here)

You would have to use

--outputs-file

and parse that

Q – where can I set the

--outputs-file

param in Seed? …and what I’m trying to do is set up integration testing, or at least take some steps towards it. e,g, on creation of a PR stage, create a user and hit the API with test data.

got it cc @Jay @Frank this is another +1 for the sst.Parameter concept which would eliminate the need to pass things through this way for tests

(I’ve flagged before that integration tests seems the missing link in the otherwise amazing SST guide… I’d be happy to author it if there was a sane Seed workflow, if the pieces aren’t all there it seems you’re pretty close)

I have a prototype of a great integration test workflow, we need to clean it up and release information about it so it'll be there soon

Ah. that’s good to know! When you say soon, are you thinking days / weeks / months… (not pinning you down, no business critical decisions riding on it, just trying to judge my efforts on this vs. other tasks)

on our roadmap it'll be sometime in april

Thanks. That’s helpful. I’m all for opinionated.

always 😄

Point being, I’m using SST + Seed because the guide was amazing and comprehensive. Such a guide has to come with opinions =]

In the meanwhile, you can fetch the output values from CloudFormation using the AWS CLI

aws cloudformation describe-stacks --stack-name my-stack --query 'Stacks[0].Outputs[?OutputKey==`MY_KEY`].OutputValue'

@Frank sorry for putting in here. Was looking to run integrations test on post deploy on seed today. Just wanted to confirm; right now we can't pass the

---outputs-file

flag to the

deploy

command on seed? I would have to run the cloudformation AWS CLI command to get the outputs, right?

That’s right @Sione. This is the best way to for now.

@thdxr Any update on your integration testing prototype?