No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

You should be able to do `pulumi preview --refresh=false`

It won't apply anything and calculate the diff using only the state, without hitting AWS

though `_terraform_._state_.RemoteStateReference` appears to try and hit my configured s3 backend

feels like it shouldn’t when not wanting to refresh and instead pulumi is just tracking an `Output`

will try at least bypass with some configuration

Regarding <https://pulumi-community.slack.com/archives/CJ909TL6P/p1637853291197200?thread_ts=1637842595.196300&amp;cid=CJ909TL6P|this>: is this expected behaviour? The implication was that `--refresh=false` should not do any network?

<@U02MP794J9E> remote state reference might not honour this, you'll need to file an issue, it's a bit of an edge case

documented <https://github.com/pulumi/pulumi-terraform/issues/633|here>

<@U02MP794J9E> as a workaround, you could wrap the remote state reference with an `if pulumi.is_dry_run()`

ty that should work (I just have a config now but this will save me another variable!)