Release/2.0.0 (#44)

* NI-36 Cpx ldn (#40)

* Update events

* Update iam permissions

* Revert changes

* Update dependencies in package.json

* Add husky pre-commit hook to run npm test

* Update build status and quality metrics badges

* test of commit and push button

* Add validation tests for message event schemas

* update to npm packages

* Update README to reflect removal of Serverless

* Update version number and engines

* Feature| NI-39 removal of serverless and Huskey (#41)

* https://eaflood.atlassian.net/browse/NI-39

* removal of husky

* changed readme back as per comments

---------

Co-authored-by: Rajesh M <[email protected]>
Co-authored-by: pwadmore-ea <[email protected]>

* Fix/sonarcloud coverage (#42)

* Fix SonarCloud coverage

https://eaflood.atlassian.net/browse/FSR-1378

* Fix SonarCloud coverage

* docs: Add release notes for version 2.0.0

---------

Co-authored-by: Niki Wycherley <[email protected]>
Co-authored-by: Rajesh M <[email protected]>
Co-authored-by: pwadmore-ea <[email protected]>

Author: 4 people

.github/workflows/ci.yml

@@ -7,12 +7,12 @@ jobs:
 
         steps:
             - name: Checkout repository
-              uses: actions/checkout@v2
+              uses: actions/checkout@v3
               with:
                 fetch-depth: 0
 
             - name: Install nodejs
-              uses: actions/setup-node@v1
+              uses: actions/setup-node@v3
               with:
                 node-version: "18.x"
 
@@ -22,19 +22,13 @@ jobs:
             - name: Run linting
               run: npm run lint
 
-            # This includes an extra run step. The sonarcloud analysis will be run in a docker container with the current
-            # folder mounted as `/github/workspace`. The problem is when the lcov.info file is generated it will reference the
-            # code in the current folder. So to enable sonarcloud to matchup code coverage with the files we use sed to update
-            # the references in lcov.info
-            # https://community.sonarsource.com/t/code-coverage-doesnt-work-with-github-action/16747/6
             - name: Run unit tests
               run: |
                 npm run test-config
                 npm run unit-test
-                sed -i 's/\/home\/runner\/work\/cap-xml\/cap-xml\//\/github\/workspace\//g' coverage/lcov.info
 
             - name: Analyse code quality
-              uses: sonarsource/sonarcloud-github-action@master
+              uses: sonarsource/sonarqube-scan-action@master
               env:
                 GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
                 SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}

.gitignore

@@ -2,9 +2,6 @@
 node_modules
 jspm_packages
 
-# Serverless directories
-.serverless
-
 #config
 config/config.json
 

config/cap.json

@@ -0,0 +1,3 @@
+{
+  "bodyXml": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\r\n<alert xmlns=\"urn:oasis:names:tc:emergency:cap:1.2\">\r\n <identifier>4eb3b7350ab7aa443650fc9351f02940E</identifier>\r\n <sender>www.gov.uk/environment-agency</sender>\r\n <sent>2024-09-17:07:02-00:00</sent>\r\n <status>Actual</status>\r\n <msgType>Alert</msgType>\r\n <source>Flood warning service</source>\r\n <scope>Public</scope>\r\n <info>\r\n <language>en-GB</language>\r\n <category>Met</category>\r\n <event><![CDATA[TEST TEST TEST 064 Issue Flood Alert EA]]></event>\r\n <urgency>Immediate</urgency><expires>2024-09-20T12:00:02-00:00</expires><area><geocode><valueName>TargetAreaCode</valueName><value><![CDATA[TESTAREA1]]></value></geocode></area></info></alert>"
+}

docs/release-2.0.0.md

@@ -0,0 +1,21 @@
+# FWIS App Release - Thursday, 20th February 2025
+
+## Information
+
+This release updates CAP-XML to move from Serverless to Terraform.
+
+## Branches
+The branch for this release is release/2.0.0
+ 
+## Tickets
+
+Tickets linked to the release in Jira: [https://eaflood.atlassian.net/projects/NI/versions/20438/tab/release-report-all-issues](https://eaflood.atlassian.net/projects/NI/versions/20438/tab/release-report-all-issues)
+
+## Instructions
+
+Execute jobs:
+
+- `MIGRATION_CX_{stage}_02_DEPLOY_API_LAMBDA`
+  - Modules to deploy: `api_gateways` and `lambda`
+
+Confirm deployment with the flood dev and test team.