Fix: aws acceptance tests

Type of change

• Bug Fix
• Feature

Please provide link to gitlab issue or ADR(Architecture Decision Record)
N/A

Does this introduce a change in the core logic?

• NO

Does this introduce a change in the cloud provider implementation, if so which cloud?

• AWS (Testing only)
• Azure
• Google Cloud
• IBM

Does this introduce a breaking change?

• NO

What is the current behavior?

aws acceptance test stage fails

What is the new/expected behavior?

aws acceptance test stage succeeds

Have you added/updated Unit Tests and Integration Tests?

N/A

Any other useful information

Fixing aws acceptance test stage by passing in relevant cucumber tag and group_id env variable

devops/aws/pipeline/override-stages.yml

+aws-acceptance-test:
+  variables:
+    CUCUMBER_OPTIONS: "--tags @default,@health,@SpatialLongitudeExtendedRange"
+    GROUP_ID: $DOMAIN
+  script:
+    - >
+      $MAVEN_BUILD . test-results.log
+      verify -DdisableXmlReport=true
+      --quiet
+      --file $ACCEPTANCE_TEST_DIR/pom.xml
+      --update-snapshots
+      -Dcucumber.filter.tags="${CUCUMBER_OPTIONS}"