@ossy/deployment-tools 1.21.2 → 1.21.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -3,6 +3,14 @@
3
3
  All notable changes to this project will be documented in this file.
4
4
  See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
5
5
 
6
+ ## 1.21.3 (2026-05-26)
7
+
8
+ **Note:** Version bump only for package @ossy/deployment-tools
9
+
10
+
11
+
12
+
13
+
6
14
  ## 1.21.2 (2026-05-26)
7
15
 
8
16
  **Note:** Version bump only for package @ossy/deployment-tools
package/README.md CHANGED
@@ -133,6 +133,38 @@ Each platform is a CDK `Stage` containing five stacks:
133
133
 
134
134
  The Elastic IP ensures the EC2 instance can be replaced (instance type changes, user data updates) without breaking DNS or CloudFormation cross-stack exports.
135
135
 
136
+ ## Destroy + redeploy
137
+
138
+ `<platformName>` is the `platformName` field in `packages/infrastructure/platforms.json` (CDK stage id). `<aws-profile>` is your AWS CLI profile for that account. List stacks: `npx cdk list --profile <aws-profile>`.
139
+
140
+ Full platform teardown:
141
+
142
+ ```bash
143
+ cd packages/deployment-tools
144
+ npx cdk destroy '<platformName>/**' --profile <aws-profile>
145
+ ```
146
+
147
+ Recreate (CDK applies stacks in dependency order):
148
+
149
+ ```bash
150
+ npx cdk deploy '<platformName>/**' --profile <aws-profile>
151
+ ```
152
+
153
+ Recycle **only the EC2 host** (keep S3, CDN, and backups):
154
+
155
+ ```bash
156
+ npx cdk destroy '<platformName>/dns' --profile <aws-profile>
157
+ npx cdk destroy '<platformName>/deployment-target' --profile <aws-profile>
158
+ npx cdk deploy '<platformName>/deployment-target' --profile <aws-profile>
159
+ npx cdk deploy '<platformName>/dns' --profile <aws-profile>
160
+ ```
161
+
162
+ Do not destroy `storage-static` unless you intend to drop media storage (bucket is `RETAIN` and may remain in the account anyway).
163
+
164
+ The S3 bucket and **AWS Backup vault** use `RETAIN` so media and recovery points survive a stack delete. CloudFront and the backup *plan* are removed with the stack.
165
+
166
+ If deploy fails with **BackupVault already exists** after a full destroy, a retained vault is still in the account (`<platformName>-static-media-backup`). Delete it in AWS Backup (empty recovery points first), or import it into the new stack.
167
+
136
168
  ## Bootstrapping a new platform
137
169
 
138
170
  ```bash
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ossy/deployment-tools",
3
- "version": "1.21.2",
3
+ "version": "1.21.3",
4
4
  "description": "Collection of scripts and tools to aid deployment of containers and static files to Amazon Web Services through GitHub Actions",
5
5
  "source": "./src/index.js",
6
6
  "main": "./src/index.js",
@@ -22,5 +22,5 @@
22
22
  "devDependencies": {
23
23
  "jest": "^27.5.1"
24
24
  },
25
- "gitHead": "5747c957d77061c1172a0ac7a6a54d1644986927"
25
+ "gitHead": "909e3d78752d07afceb60af78784987f6fcea8b7"
26
26
  }
@@ -39,6 +39,7 @@ class StorageStaticStack extends Stack {
39
39
  })
40
40
 
41
41
  const backupVault = new BackupVault(this, 'StaticMediaBackupVault', {
42
+ backupVaultName: `${props.config.platformName}-static-media-backup`,
42
43
  removalPolicy: RemovalPolicy.RETAIN
43
44
  })
44
45