Merge pull request #600 from isomerpages/release/0.14.0

Release/0.14.0

CHANGELOG.md

@@ -4,8 +4,21 @@ All notable changes to this project will be documented in this file. Dates are d
 
 Generated by [`auto-changelog`](https://github.com/CookPete/auto-changelog).
 
+#### [v0.14.0](https://github.com/isomerpages/isomercms-backend/compare/v0.13.0...v0.14.0)
+
+- Fix/frontmatter for link resources [`#598`](https://github.com/isomerpages/isomercms-backend/pull/598)
+- build(deps): bump json5 from 1.0.1 to 1.0.2 [`#599`](https://github.com/isomerpages/isomercms-backend/pull/599)
+- fix(usersservice): remove explicit `findOrCreate` calls [`#594`](https://github.com/isomerpages/isomercms-backend/pull/594)
+- fix: package.json & package-lock.json to reduce vulnerabilities [`#581`](https://github.com/isomerpages/isomercms-backend/pull/581)
+- build(deps): bump minimatch from 3.0.4 to 3.1.2 [`#580`](https://github.com/isomerpages/isomercms-backend/pull/580)
+- build(deps): bump decode-uri-component from 0.2.0 to 0.2.2 [`#579`](https://github.com/isomerpages/isomercms-backend/pull/579)
+- chore(readme instructions for db migrations): update usage of VPN [`#551`](https://github.com/isomerpages/isomercms-backend/pull/551)
+- release(0.13.0): merge to develop [`#506`](https://github.com/isomerpages/isomercms-backend/pull/506)
+
 #### [v0.13.0](https://github.com/isomerpages/isomercms-backend/compare/v0.12.0...v0.13.0)
 
+> 29 September 2022
+
 - Chore/update dependencies [`#504`](https://github.com/isomerpages/isomercms-backend/pull/504)
 - build(deps): bump vm2 from 3.9.7 to 3.9.11 [`#505`](https://github.com/isomerpages/isomercms-backend/pull/505)
 - release(0.12.0): merge to develop [`#502`](https://github.com/isomerpages/isomercms-backend/pull/502)
@@ -77,15 +90,15 @@ Generated by [`auto-changelog`](https://github.com/CookPete/auto-changelog).
 - Feat/add access token table [`#441`](https://github.com/isomerpages/isomercms-backend/pull/441)
 - Refactor/consolidate misc GitHub requests [`#440`](https://github.com/isomerpages/isomercms-backend/pull/440)
 - 0.5.0 [`#434`](https://github.com/isomerpages/isomercms-backend/pull/434)
-- Fix/migrate script [`#432`](https://github.com/isomerpages/isomercms-backend/pull/432)
-- Feat/move whitelist into database [`#422`](https://github.com/isomerpages/isomercms-backend/pull/422)
-- Refactor/use test fixture [`#430`](https://github.com/isomerpages/isomercms-backend/pull/430)
-- Chore: remove duplicate validation in User model [`#429`](https://github.com/isomerpages/isomercms-backend/pull/429)
 
 #### [v0.5.0](https://github.com/isomerpages/isomercms-backend/compare/v0.4.0...v0.5.0)
 
-> 14 April 2022
+> 21 April 2022
 
+- Fix/migrate script [`#432`](https://github.com/isomerpages/isomercms-backend/pull/432)
+- Feat/move whitelist into database [`#422`](https://github.com/isomerpages/isomercms-backend/pull/422)
+- Refactor/use test fixture [`#430`](https://github.com/isomerpages/isomercms-backend/pull/430)
+- Chore: remove duplicate validation in User model [`#429`](https://github.com/isomerpages/isomercms-backend/pull/429)
 - build(deps-dev): bump eslint-config-prettier from 8.1.0 to 8.5.0 [`#371`](https://github.com/isomerpages/isomercms-backend/pull/371)
 - build(deps): bump async from 3.2.0 to 3.2.3 [`#424`](https://github.com/isomerpages/isomercms-backend/pull/424)
 - chore(mergify): change to lower case [`#425`](https://github.com/isomerpages/isomercms-backend/pull/425)

README.md

@@ -24,14 +24,7 @@ where versionType corresponds to npm version types. This only works on non-Windo
 
 The following steps are needed before you can run migrations on a remote database in a private subnet of an AWS VPC.
 
-First, you will need to ensure that your current device IP address is whitelisted to use the EC2 instance.
-
-- Log into the AWS console and navigate to the EC2 Dashboard.
-- Navigate to the Security Groups tab by looking at the Network & Security section in the left pane and clicking on the Security Groups tab.
-- Look for the security group titled `cms-bastion-<ENVIRONMENT>`, where `<ENVIRONMENT>` is either staging or production. Click on the security group and then the Inbound rules tab.
-- If you see your IP address in the Inbound rules whitelist, you are done with this step.
-- If your IP address does not exist in the Inbound rules whitelist, click on the Edit inbound rules button.
-- Click on the Add rule button. Select SSH as the Type, and select My IP as the Source. Give a meaningful description for the security rule, e.g. WeWork City House. Click on Save rules to complete this step.
+First, ensure that you are connected to [AWS VPN](https://www.notion.so/opengov/Instructions-to-use-OGP-s-AWS-VPN-e67226703cac459999b84c02200a3940) as only the VPN is whitelisted to use the EC2 instance<sup>1</sup>.
 
 Next, you will require the correct environment variables and credentials.
 
@@ -56,3 +49,12 @@ Finally, we want to run the migration script.
 - Open another terminal window.
 - Run `source .env`
 - Run `npx sequelize-cli db:migrate`
+
+---
+
+<sup>1</sup> To check whitelisted IPs in EC2 instance,
+
+- Log into the AWS console and navigate to the EC2 Dashboard.
+- Navigate to the Security Groups tab by looking at the Network & Security section in the left pane and clicking on the Security Groups tab.
+- Look for the security group titled `cms-bastion-<ENVIRONMENT>`, where `<ENVIRONMENT>` is either staging or production. Click on the security group and then the Inbound rules tab.
+- If you see your IP address in the Inbound rules whitelist, you are done with this step.