Victor Navarro
Victor Navarro
@wilfredjonathanjames wouldn't this break as soon as you deploy to a different stage since the names would be different?
sorry i thought that you wanted to hardcode the name either way, after running `sst deploy --stage staging` you would get a different `sst-env.d.ts` than when running `sst deploy --stage...
for the secret to be updated you need to deploy the environment via `sst deploy` or `sst dev` maybe you were checking the env variable before running those commands?
what you see with your reproduction steps is expected, not a bug this happens because internally the `shell` loads secrets from the completed deployment state while `secret list` reads them...
let's wait on merging #6271 first
duplicate of #6179
thanks for the contribution @smith558 could we symlink the root README.md instead?
thankfully Pulumi now has a `--exclude` flag: https://www.pulumi.com/blog/excluding-targets-from-stack-operations/ we need to update the Pulumi version to be able to use it: #5944 we'll need to add the flag to the...
> Won't it delete the component? yes, it would
this should be as easy as setting `deleteBeforeReplace` to false and activating the Pulumi [`allowMajorVersionUpgrade`](https://www.pulumi.com/registry/packages/aws/api-docs/rds/instance/#allowmajorversionupgrade_nodejs) to true PR coming soon