From e449541e81f3cfbe8895c36384db37a60a582ad2 Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Mon, 11 Aug 2025 19:39:48 +0000 Subject: [PATCH 1/2] [pre-commit.ci] pre-commit autoupdate MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit updates: - [github.com/pre-commit/pre-commit-hooks: v3.2.0 β†’ v6.0.0](https://github.com/pre-commit/pre-commit-hooks/compare/v3.2.0...v6.0.0) - [github.com/gruntwork-io/pre-commit: v0.1.10 β†’ v0.1.30](https://github.com/gruntwork-io/pre-commit/compare/v0.1.10...v0.1.30) - [github.com/pre-commit/mirrors-prettier: v2.2.1 β†’ v4.0.0-alpha.8](https://github.com/pre-commit/mirrors-prettier/compare/v2.2.1...v4.0.0-alpha.8) --- .pre-commit-config.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml index a20dd1f..5df3c1c 100644 --- a/.pre-commit-config.yaml +++ b/.pre-commit-config.yaml @@ -1,6 +1,6 @@ repos: - repo: https://github.com/pre-commit/pre-commit-hooks - rev: v3.2.0 + rev: v6.0.0 hooks: - id: check-added-large-files args: ["--maxkb=500"] @@ -24,7 +24,7 @@ repos: - id: trailing-whitespace args: [--markdown-linebreak-ext=md] - repo: https://github.com/gruntwork-io/pre-commit - rev: v0.1.10 + rev: v0.1.30 hooks: - id: shellcheck exclude: | @@ -32,6 +32,6 @@ repos: gradlew )$ - repo: https://github.com/pre-commit/mirrors-prettier - rev: v2.2.1 + rev: v4.0.0-alpha.8 hooks: - id: prettier From 9e4d47ed8c954a60b8b441a63c5989c2692267d0 Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Mon, 11 Aug 2025 19:52:27 +0000 Subject: [PATCH 2/2] [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --- webapp/docs/foresight-api.mdx | 4 ---- webapp/docs/foresight-install-ECS.mdx | 5 ----- webapp/docs/foresight-ops-diagnostic.mdx | 2 +- webapp/src/pages/index.js | 2 +- webapp/src/partials/foresight-api-header.md | 4 ---- 5 files changed, 2 insertions(+), 15 deletions(-) diff --git a/webapp/docs/foresight-api.mdx b/webapp/docs/foresight-api.mdx index a69b49e..cfdfd6b 100644 --- a/webapp/docs/foresight-api.mdx +++ b/webapp/docs/foresight-api.mdx @@ -64,7 +64,6 @@ curl $FORESIGHT_API_BASE_URL/sage/application/ -H "Authorization: bearer $TOKEN" The quickest way to get started is to use our Postman request collection. The following steps will help you get up and running. 1. **Import the CloudScend Foresight Postman Collection** - - Select downloaded Foresight postman collection 2. **Configure Postman Environment** - - Setup a new environment in Postman. Click New -> Environment. - Name the new environment _Foresight API_ - Add the following variables: @@ -85,7 +83,6 @@ The quickest way to get started is to use our Postman request collection. The fo - Click Add to create 3. **Authenticate** - - 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. - 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: - 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 - View [Postman Documentation on OAuth2 Authentication](https://learning.postman.com/docs/sending-requests/authorization/#oauth-20) for more info. 4. **Explore the API** - - Execute any of the requests within the collection - Refer to this documentation for the requirements of each request diff --git a/webapp/docs/foresight-install-ECS.mdx b/webapp/docs/foresight-install-ECS.mdx index 3cf2426..aad5a94 100644 --- a/webapp/docs/foresight-install-ECS.mdx +++ b/webapp/docs/foresight-install-ECS.mdx @@ -12,7 +12,6 @@ sidebar_label: Installing CloudScend Foresight to AWS ECS - You are familiar with AWS ECS Environments - Access to functional AWS ECS Environment - Technical Knowledge of the following - - Docker - Docker Compose - AWS @@ -101,7 +100,6 @@ Additional information on installing AWS CLI is available at [AWS Amazon](https: 1. Obtain your deployment code repository from the [CloudScend Foresight ECS Deployment location](PUT A LINK IN HERE?). 2. Deployment order of CloudScend Foresight containers: - - Commondata Database - Commondata Backend - Metabase DB @@ -147,7 +145,6 @@ For example, the following describe and register statements create task definiti 4. Create ECS Services - If your administrator has chosen the Fargate service, then create ECS Fargate Services - - 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. ``` @@ -156,7 +153,6 @@ For example, the following describe and register statements create task definiti :::note It’s recommended to run Elasticsearch on Fargate due to recent compatibility contingencies. - - To fix paging issue on Elasticsearch EC2 attempt to add this command to the instances: **THIS SAYS EC2 BUT DEALING WITH FARGATE** - sudo sysctl -w vm.max_map_count=262144 - 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 ``` - If your administrator has chosen the EC2 service, then create ECS EC2 Services - - 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. ``` diff --git a/webapp/docs/foresight-ops-diagnostic.mdx b/webapp/docs/foresight-ops-diagnostic.mdx index 81e2aa0..a5ecb06 100644 --- a/webapp/docs/foresight-ops-diagnostic.mdx +++ b/webapp/docs/foresight-ops-diagnostic.mdx @@ -35,13 +35,13 @@ As an administrator there may be times when you need to examine the logs for pos ``` brew install awscli ``` + - 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. 3. Contact your AWS admin to get an AWS account setup and loaded in - You will need: - 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. - The admin needs to add you into the AWS cluster. 4. Setup your account information into the aws cli - - Run aws configure in your terminal and it will prompt you for four items. ``` diff --git a/webapp/src/pages/index.js b/webapp/src/pages/index.js index 73bd04f..3f3bb4b 100644 --- a/webapp/src/pages/index.js +++ b/webapp/src/pages/index.js @@ -74,7 +74,7 @@ function Home() { diff --git a/webapp/src/partials/foresight-api-header.md b/webapp/src/partials/foresight-api-header.md index 0240e28..fea4e75 100644 --- a/webapp/src/partials/foresight-api-header.md +++ b/webapp/src/partials/foresight-api-header.md @@ -64,7 +64,6 @@ curl $FORESIGHT_API_BASE_URL/sage/application/ -H "Authorization: bearer $TOKEN" The quickest way to get started is to use our Postman request collection. The following steps will help you get up and running. 1. **Import the CloudScend Foresight Postman Collection** - - Select downloaded Foresight postman collection 2. **Configure Postman Environment** - - Setup a new environment in Postman. Click New -> Environment. - Name the new environment _Foresight API_ - Add the following variables: @@ -84,7 +82,6 @@ The quickest way to get started is to use our Postman request collection. The fo - Click Add to create 3. **Authenticate** - - 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. - 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: - 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 - View [Postman Documentation on OAuth2 Authentication](https://learning.postman.com/docs/sending-requests/authorization/#oauth-20) for more info. 4. **Explore the API** - - Execute any of the requests within the collection - Refer to this documentation for the requirements of each request