Skip to content

Commit f899485

Browse files
[pre-commit.ci] auto fixes from pre-commit.com hooks
for more information, see https://pre-commit.ci
1 parent 94242df commit f899485

File tree

5 files changed

+2
-15
lines changed

5 files changed

+2
-15
lines changed

webapp/docs/foresight-api.mdx

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,6 @@ curl $FORESIGHT_API_BASE_URL/sage/application/ -H "Authorization: bearer $TOKEN"
6464
The quickest way to get started is to use our Postman request collection. The following steps will help you get up and running.
6565

6666
1. **Import the CloudScend Foresight Postman Collection**
67-
6867
- <a
6968
href={useBaseUrl("/data/foresight-api.postman_collection.json")}
7069
download
@@ -75,7 +74,6 @@ The quickest way to get started is to use our Postman request collection. The fo
7574
- From Postman, Import -> Select downloaded Foresight postman collection
7675

7776
2. **Configure Postman Environment**
78-
7977
- Setup a new environment in Postman. Click New -> Environment.
8078
- Name the new environment _Foresight API_
8179
- Add the following variables:
@@ -85,7 +83,6 @@ The quickest way to get started is to use our Postman request collection. The fo
8583
- Click Add to create
8684

8785
3. **Authenticate**
88-
8986
- In the Authorization tab for the collection, select OAuth 2.0 from the Type dropdown list. By default Postman will append the access token to Bearer in the Authorization header for your request.
9087
- To request an access token, fill out the fields in the Configure New Token section. There are several ways to configure based on the Grant Type you want to use. For the Password Credentials grant type enter the following details:
9188
- Access Token URL: {{loginBaseUrl}}/auth/realms/appmod/protocol/openid-connect/token
@@ -100,7 +97,6 @@ The quickest way to get started is to use our Postman request collection. The fo
10097
- View [Postman Documentation on OAuth2 Authentication](https://learning.postman.com/docs/sending-requests/authorization/#oauth-20) for more info.
10198

10299
4. **Explore the API**
103-
104100
- Execute any of the requests within the collection
105101
- Refer to this documentation for the requirements of each request
106102

webapp/docs/foresight-install-ECS.mdx

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,6 @@ sidebar_label: Installing CloudScend Foresight to AWS ECS
1212
- You are familiar with AWS ECS Environments
1313
- Access to functional AWS ECS Environment
1414
- Technical Knowledge of the following
15-
1615
- Docker
1716
- Docker Compose
1817
- AWS
@@ -101,7 +100,6 @@ Additional information on installing AWS CLI is available at [AWS Amazon](https:
101100
1. Obtain your deployment code repository from the [CloudScend Foresight ECS Deployment location](PUT A LINK IN HERE?).
102101

103102
2. Deployment order of CloudScend Foresight containers:
104-
105103
- Commondata Database
106104
- Commondata Backend
107105
- Metabase DB
@@ -147,7 +145,6 @@ For example, the following describe and register statements create task definiti
147145
4. Create ECS Services
148146

149147
- If your administrator has chosen the Fargate service, then create ECS Fargate Services
150-
151148
- To create a service with Fargate, run similar AWS CLI command below for each ECS Task Definition previously created. Below is an example using the commondata-db container. Ensure you use the correct network and cluster values for your environment.
152149

153150
```
@@ -156,7 +153,6 @@ For example, the following describe and register statements create task definiti
156153

157154
:::note
158155
It’s recommended to run Elasticsearch on Fargate due to recent compatibility contingencies.
159-
160156
- To fix paging issue on Elasticsearch EC2 attempt to add this command to the instances: **THIS SAYS EC2 BUT DEALING WITH FARGATE**
161157
- sudo sysctl -w vm.max_map_count=262144
162158
- sudo sysctl -w fs.file-max=65536
@@ -225,7 +221,6 @@ Below find an example of a successful output when task definition is properly re
225221
```
226222

227223
- If your administrator has chosen the EC2 service, then create ECS EC2 Services
228-
229224
- To create a service with ECS EC2, run simialiar AWS CLI command for each Task Definition previously created. Below is an example using the commondata container. Ensure you use the correct network and cluster values for your environment.
230225

231226
```

webapp/docs/foresight-ops-diagnostic.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,13 +35,13 @@ As an administrator there may be times when you need to examine the logs for pos
3535
```
3636
brew install awscli
3737
```
38+
3839
- If you don't want to or cannot use brew, there are other options discussed here: https://stackoverflow.com/questions/26574232/aws-cli-path-settings.
3940
3. Contact your AWS admin to get an AWS account setup and loaded in
4041
- You will need:
4142
- An access Key on AWS - either create one or update the IAM user's key. This should be a CSV but preferably given to user secure channels.
4243
- The admin needs to add you into the AWS cluster.
4344
4. Setup your account information into the aws cli
44-
4545
- Run aws configure in your terminal and it will prompt you for four items.
4646

4747
```

webapp/src/pages/index.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ function Home() {
7474
<Link
7575
className={clsx(
7676
"button button--outline button--secondary button--lg",
77-
styles.getStarted
77+
styles.getStarted,
7878
)}
7979
to={useBaseUrl("docs/foresight-cloud-app-mod-overview")}
8080
>

webapp/src/partials/foresight-api-header.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,6 @@ curl $FORESIGHT_API_BASE_URL/sage/application/ -H "Authorization: bearer $TOKEN"
6464
The quickest way to get started is to use our Postman request collection. The following steps will help you get up and running.
6565

6666
1. **Import the CloudScend Foresight Postman Collection**
67-
6867
- <a
6968
href={useBaseUrl("/data/foresight-api.postman_collection.json")}
7069
download
@@ -74,7 +73,6 @@ The quickest way to get started is to use our Postman request collection. The fo
7473
- From Postman, Import -> Select downloaded Foresight postman collection
7574

7675
2. **Configure Postman Environment**
77-
7876
- Setup a new environment in Postman. Click New -> Environment.
7977
- Name the new environment _Foresight API_
8078
- Add the following variables:
@@ -84,7 +82,6 @@ The quickest way to get started is to use our Postman request collection. The fo
8482
- Click Add to create
8583

8684
3. **Authenticate**
87-
8885
- In the Authorization tab for the collection, select OAuth 2.0 from the Type dropdown list. By default Postman will append the access token to Bearer in the Authorization header for your request.
8986
- To request an access token, fill out the fields in the Configure New Token section. There are several ways to configure based on the Grant Type you want to use. For the Password Credentials grant type enter the following details:
9087
- Access Token URL: {{loginBaseUrl}}/auth/realms/appmod/protocol/openid-connect/token
@@ -99,7 +96,6 @@ The quickest way to get started is to use our Postman request collection. The fo
9996
- View [Postman Documentation on OAuth2 Authentication](https://learning.postman.com/docs/sending-requests/authorization/#oauth-20) for more info.
10097

10198
4. **Explore the API**
102-
10399
- Execute any of the requests within the collection
104100
- Refer to this documentation for the requirements of each request
105101

0 commit comments

Comments
 (0)