From 1dfab60c4eb3968887505842024359a557b29b28 Mon Sep 17 00:00:00 2001 From: vonbraunbates Date: Mon, 6 Jan 2025 16:20:00 +0000 Subject: [PATCH] Update CONTRIBUTING.md --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 06cdf82..f4ef9dc 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -51,8 +51,8 @@ Use the `--force-reinstall` flag to replace an existing version if necessary. T `aws-vault exec ` If you're not sure which profile to use, consult `aws-vault list` or for even more detail, your `~/.aws/config` file. 3. Log in to the Pulumi backend with `pulumi login --cloud-url s3://data-engineering-pulumi.analytics.justice.gov.uk`. -4. Run `pulumi stack select` and pick `data-engineering-exports`. -5. Run `pulumi stack` to check you can see what's currently deployed. +4. Run `pulumi stack select` and pick `data-engineering-exports`(which may be out-of-sight, just keep hitting the up arrow). +5. Run `pulumi stack` to check you can see what's currently deployed. If asked for a passphrase, hit return. 6. Run `pulumi preview` to check the resources look correct. Use the `--diff` flag to see details. You may see changes to update the local archive path, which can be ignored. If you are using a different version of `pulumi-aws` to the current deplyment you may see changes relating to the provider, you can avoid these by installing the specific version curently in use, for example, `pip install --force-reinstall pulumi-aws==5.40.0`.