-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Added support for latest SDKs (#272)
* updated demo app - maps, places and routes * updated package-lock.json * removed unecessary pngs * added new navigation and updated tests accordingly * updated icons and added desc * updated README * updated link opening and test * updates * resolved comment * updated template for unauth geofences * added check on color scheme for hybrid and satellite map styles * resolved bugs * fixed e2e tests * resolved ts issue * fixed and updated e2e tests * resolved bugs * updated CF templates * updates * updated template * updated template * updated workflow files, README and removed ap-southeast-1 region * fixed e2e and unit test issues * resolved comments * resolved comments * resolved comments * updated e2e * added wait for network calls * resolved test issues * udpated tests * updated test * removed log * added retries * optimized route layer data * resolved suggest API issue * resolved search issue * implemented ALS-1835 and ALS-1836, updated geo-places and geo-routes clients * resolved issues and updated deps * updated sidebar and responsive navigation * resolved comment * resolved comment * updated place popup with opening hours, websites and phone numbers * resolved opening hours display issue --------- Co-authored-by: Ahmad Azizi <[email protected]> Co-authored-by: Mike Balfour <[email protected]> Co-authored-by: wadhawh <[email protected]>
- Loading branch information
1 parent
b1bf7a4
commit 3eab7c3
Showing
154 changed files
with
10,709 additions
and
15,157 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,20 +2,34 @@ | |
|
||
## Requirements | ||
|
||
1. Run the template from `/extra/cloudformation/default-unauth-resources-template.yaml` to create a cloudformation stack on AWS in `us-east-1` region using your own AWS account and get `IdentityPoolId`, `PinPointAppId`, `WebSocketUrl` from stack output's tab. | ||
1. Run the template from `/extra/cloudformation/unauth-resources.yaml` to create AWS CloudFormation stack in `us-east-1` region and get `Region`, `ApiKey`, `IdentityPoolId`, `PinPointAppId`, `WebSocketUrl` from stack output's tab. | ||
- `Region` value will be added to `.env` file against `VITE_AWS_API_KEY_REGIONS`. | ||
- `ApiKey` value will be added to `.env` file against `VITE_AWS_API_KEYS`. | ||
- In stack output's tab only the ApiKey name is visible, in order to get the ApiKey value | ||
- Navigate to Amazon Location Service | ||
- Click on "API keys" from the left navigation pane | ||
- Click on the ApiKey name | ||
- Copy the ApiKey value | ||
- `IdentityPoolId` value will be added to `.env` file against `VITE_AWS_COGNITO_IDENTITY_POOL_IDS` and `VITE_PINPOINT_IDENTITY_POOL_ID`. | ||
- `PinPointAppId` value will be added to `.env` file against `VITE_PINPOINT_APPLICATION_ID`. | ||
- `WebSocketUrl` value will be added to `.env` file against `VITE_AWS_WEB_SOCKET_URLS`. | ||
2. Run the template from `/extra/cloudformation/default-unauth-resources-template.yaml` to create a cloudformation stack on AWS in `ap-southeast-1` region using your own AWS account and get `IdentityPoolId`, `WebSocketUrl` from stack output's tab **[Necessary if you want *GrabMaps* to be enabled]**. | ||
- `IdentityPoolId` value will be added to `.env` file against `VITE_AWS_COGNITO_IDENTITY_POOL_IDS` **(comma separated for multiple values)**. | ||
- `WebSocketUrl` value will be added to `.env` file against `VITE_AWS_WEB_SOCKET_URLS` **(comma separated for multiple values)**. | ||
3. Value for `VITE_AWS_CF_TEMPLATE`, `VITE_APPLE_APP_STORE_LINK`, `VITE_GOOGLE_PLAY_STORE_LINK` can be added as it is to `.env` file from `.env.examples`. | ||
- --- | ||
***Note*** | ||
* Pinpoint and Translate resosurces are only created in `us-east-1` which are required for the analytics feature and running translation scripts. | ||
* Make sure to run the above stack in `eu-west-1` as well to support multiple regions. | ||
* The `Region`, `ApiKey`, `IdentityPoolId`, `WebSocketUrl` values from stack output's tab can be added to `.env` file against the respective keys. | ||
* The `VITE_AWS_API_KEY_REGIONS`, `VITE_AWS_API_KEYS`, `VITE_AWS_COGNITO_IDENTITY_POOL_IDS`, `VITE_AWS_WEB_SOCKET_URLS` keys in `.env` file should be comma separated for multiple values and must be in same order for all variables. | ||
--- | ||
2. Upload the CF template from `/extra/cloudformation/auth-resources.yaml` to S3 bucket and add the link with the following prefix `https://us-east-1.console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/create?stackName=amazon-location-resources-setup&templateURL=<LINK_TO_UPLOADED_CF_TEMPLATE>` to the key `VITE_AWS_CF_TEMPLATE` in `.env` file. | ||
3. Value for `VITE_APPLE_APP_STORE_LINK`, `VITE_GOOGLE_PLAY_STORE_LINK` can be added as it is to `.env` file from `.env.examples`. | ||
4. Value for `VITE_APP_VERSION` needs to be populated with the correct version at the time of deployment in the following format `2.1.0`. | ||
5. Values for `VITE_MIGRATE_FROM_GOOGLE_MAPS_PAGE`, `VITE_MIGRATE_A_WEB_APP_PAGE`, `VITE_MIGRATE_AN_ANDROID_APP_PAGE`, `VITE_MIGRATE_AN_IOS_APP_PAGE`, `VITE_MIGRATE_A_WEB_SERVICE_PAGE` and `VITE_PRICING_PAGE` can either be `1` or `0` to either enable or disable the respective pages. | ||
6. Values for `VITE_SHOW_NEW_NAVIGATION` can either be `1` or `0` to either enable or disable the new navigation, turning it off would show the current navigation instead. | ||
|
||
#### Env keys required in `.env` file, see `.env.example` for reference | ||
|
||
> VITE_AWS_API_KEY_REGIONS<br /> | ||
> VITE_AWS_API_KEYS<br /> | ||
> VITE_AWS_COGNITO_IDENTITY_POOL_IDS<br /> | ||
> VITE_AWS_WEB_SOCKET_URLS<br /> | ||
> VITE_PINPOINT_IDENTITY_POOL_ID<br /> | ||
|
@@ -57,8 +71,6 @@ Open [http://localhost:3000](http://localhost:3000) to view it in the browser. | |
#### Env keys required in `cypress.env.json` file, see `cypress.env.json.example` for reference. | ||
|
||
> WEB_DOMAIN<br /> | ||
> WEB_DOMAIN_USERNAME<br /> | ||
> WEB_DOMAIN_PASSWORD<br /> | ||
> IDENTITY_POOL_ID<br /> | ||
> USER_DOMAIN<br /> | ||
> USER_POOL_CLIENT_ID<br /> | ||
|
@@ -71,8 +83,8 @@ Open [http://localhost:3000](http://localhost:3000) to view it in the browser. | |
#### If you are configuring Github actions for the E2E tests, make sure to add the below env keys to the secrets section of the repo. | ||
|
||
1. The `/extra/cloudformation/main-cf-template.yaml` needs to be deployed on one of the production accounts in the `us-east-1` region. | ||
2. Download this `/extra/cloudformation/main-cf-template.yaml` on local machine. | ||
1. The `/extra/cloudformation/auth-resources.yaml` needs to be deployed on one of the production accounts in the `us-east-1` region. | ||
2. Download this `/extra/cloudformation/auth-resources.yaml` on local machine. | ||
3. Login to AWS console. | ||
4. Go to CloudFormation service. | ||
5. Click on Create Stack → Upload a Template file → Select the template file downloaded above. | ||
|
@@ -84,32 +96,29 @@ Open [http://localhost:3000](http://localhost:3000) to view it in the browser. | |
11. Add all keys from `.env` file to the secrets section of the repo as well from the above Requirements section. | ||
``` | ||
> WEB_DOMAIN: "http://localhost:3000" | ||
> WEB_DOMAIN_USERNAME: "XXXXX" // This is the username for the web domain (only required for dev and qa environments, not needed for prod environment) | ||
> WEB_DOMAIN_PASSWORD: "XXXXX" // This is the password for the web domain (only required for dev and qa environments, not needed for prod environment) | ||
> IDENTITY_POOL_ID: "XX-XXXX-X:XXXXXXXX-XXXX-1234-abcd-1234567890ab" // Stack output as IdentityPoolId | ||
> USER_DOMAIN: "https://XXXXXXXXXXXX.XXXX.XX-XXXX-X.amazoncognito.com/" // Stack output as UserDomain | ||
> USER_POOL_CLIENT_ID: "XXXXXXXXXXXX" // Stack output as UserPoolClientId | ||
> USER_POOL_ID: "XX-XXXX-X_XXXXXXXXXX" // Stack output as UserPoolId | ||
> WEB_SOCKET_URL: "XXXXXXXXXXX-ats.iot.us-east-1.amazonaws.com" // Stack output as WebSocketUrl | ||
> COGNITO_EMAIL: "[email protected]" // Stack output as UserEmail | ||
> COGNITO_PASSWORD: "XXXXXX" // This is the password for the cognito user (received on registered email) | ||
> VITE_AWS_API_KEY_REGIONS | ||
> VITE_AWS_API_KEYS | ||
> VITE_AWS_COGNITO_IDENTITY_POOL_IDS | ||
> VITE_AWS_WEB_SOCKET_URLS | ||
> VITE_PINPOINT_IDENTITY_POOL_ID | ||
> VITE_PINPOINT_APPLICATION_ID | ||
> VITE_AWS_CF_TEMPLATE | ||
> VITE_APPLE_APP_STORE_LINK | ||
> VITE_GOOGLE_PLAY_STORE_LINK | ||
> VITE_DATA_FILES_URL | ||
> VITE_SAMPLES_LIST_FILENAME | ||
> VITE_APP_VERSION | ||
> VITE_MIGRATE_FROM_GOOGLE_MAPS_PAGE | ||
> VITE_MIGRATE_A_WEB_APP_PAGE | ||
> VITE_MIGRATE_AN_ANDROID_APP_PAGE | ||
> VITE_MIGRATE_AN_IOS_APP_PAGE | ||
> VITE_MIGRATE_A_WEB_SERVICE_PAGE | ||
> VITE_PRICING_PAGE | ||
> VITE_CUSTOM_ASSETS_URL | ||
> VITE_SHOW_NEW_NAVIGATION | ||
``` | ||
|
||
|
@@ -122,8 +131,8 @@ Runs Cypress tests to completion in a headed chrome browser. | |
#### Env keys required in `security-tests/.env` file, see `security-tests/.env.example` for reference. | ||
|
||
> IDENTITY_POOL_ID</br> | ||
> USER_POOL_ID</br> | ||
> USER_POOL_CLIENT_ID</br> | ||
> USER_POOL_ID</br> | ||
> COGNITO_EMAIL</br> | ||
> COGNITO_PASSWORD</br> | ||
> IAM_AUTH_ROLE_NAME</br> | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.