Tezos. Run pre-merge tools

vlasonfa · vlasonfa · commit f5f2d0948370 · 2024-08-01T18:29:42.000+10:00
diff --git a/docs/setup-cloud9.md b/docs/setup-cloud9.md
@@ -1,6 +1,6 @@
 # AWS CloudShell
 
-To begin, ensure you login to your AWS account with permissions to create and modify resources in IAM, EC2, EBS, VPC, S3, KMS, and Secrets Manager. 
+To begin, ensure you login to your AWS account with permissions to create and modify resources in IAM, EC2, EBS, VPC, S3, KMS, and Secrets Manager.
 
 From the AWS Management Console, open the [AWS CloudShell](https://docs.aws.amazon.com/cloudshell/latest/userguide/welcome.html), a web-based shell environment. If unfamiliar, review the [2-minute YouTube video](https://youtu.be/fz4rbjRaiQM) for an overview and check out [CloudShell with VPC environment](https://docs.aws.amazon.com/cloudshell/latest/userguide/creating-vpc-environment.html) that we'll use to test nodes API from internal IP address space.
 
diff --git a/lib/bsc/README.md b/lib/bsc/README.md
@@ -72,7 +72,7 @@ This is the Well-Architected checklist for BSC nodes implementation of the AWS B
 
 ### Open AWS CloudShell
 
-To begin, ensure you login to your AWS account with permissions to create and modify resources in IAM, EC2, EBS, VPC, S3, KMS, and Secrets Manager. 
+To begin, ensure you login to your AWS account with permissions to create and modify resources in IAM, EC2, EBS, VPC, S3, KMS, and Secrets Manager.
 
 From the AWS Management Console, open the [AWS CloudShell](https://docs.aws.amazon.com/cloudshell/latest/userguide/welcome.html), a web-based shell environment. If unfamiliar, review the [2-minute YouTube video](https://youtu.be/fz4rbjRaiQM) for an overview and check out [CloudShell with VPC environment](https://docs.aws.amazon.com/cloudshell/latest/userguide/creating-vpc-environment.html) that we'll use to test nodes API from internal IP address space.
 
@@ -247,7 +247,7 @@ It will return `false` if the node is in sync. If `eth_syncing` returns anything
    }
 ```
 
-> **NOTE:** 
+> **NOTE:**
 > - *By default and for security reasons the load balancer is available only from within the default VPC in the region where it is deployed. It is not available from the Internet and is not open for external connections. Before opening it up please make sure you protect your RPC APIs.*
 
 3. Once the initial synchronization is done, you should be able to access the RPC API of that node from within the same VPC. The RPC port is not exposed to the Internet. Run the following query against the private IP of the single RPC node you deployed:
diff --git a/lib/ethereum/README.md b/lib/ethereum/README.md
@@ -59,7 +59,7 @@ This is the Well-Architected checklist for Ethereum nodes implementation of the
 
 ### Open AWS CloudShell
 
-To begin, ensure you login to your AWS account with permissions to create and modify resources in IAM, EC2, EBS, VPC, S3, KMS, and Secrets Manager. 
+To begin, ensure you login to your AWS account with permissions to create and modify resources in IAM, EC2, EBS, VPC, S3, KMS, and Secrets Manager.
 
 From the AWS Management Console, open the [AWS CloudShell](https://docs.aws.amazon.com/cloudshell/latest/userguide/welcome.html), a web-based shell environment. If unfamiliar, review the [2-minute YouTube video](https://youtu.be/fz4rbjRaiQM) for an overview and check out [CloudShell with VPC environment](https://docs.aws.amazon.com/cloudshell/latest/userguide/creating-vpc-environment.html) that we'll use to test nodes API from internal IP address space.
 
diff --git a/lib/fantom/README.md b/lib/fantom/README.md
@@ -71,7 +71,7 @@ This is the Well-Architected checklist for Fantom nodes implementation of the AW
 ## Setup Instructions
 
 ### Open AWS CloudShell
-To begin, ensure you login to your AWS account with permissions to create and modify resources in IAM, EC2, EBS, VPC, S3, KMS, and Secrets Manager. 
+To begin, ensure you login to your AWS account with permissions to create and modify resources in IAM, EC2, EBS, VPC, S3, KMS, and Secrets Manager.
 
 From the AWS Management Console, open the [AWS CloudShell](https://docs.aws.amazon.com/cloudshell/latest/userguide/welcome.html), a web-based shell environment. If unfamiliar, review the [2-minute YouTube video](https://youtu.be/fz4rbjRaiQM) for an overview and check out [CloudShell with VPC environment](https://docs.aws.amazon.com/cloudshell/latest/userguide/creating-vpc-environment.html) that we'll use to test nodes API from internal IP address space.
 
diff --git a/lib/fantom/lib/assets/fantom-checker/syncchecker-fantom.sh b/lib/fantom/lib/assets/fantom-checker/syncchecker-fantom.sh
@@ -25,7 +25,7 @@ FANTOM_SYNC_STATS=$(su bcuser -c '/home/bcuser/go-opera/build/opera attach --dat
 if [ -n "$FANTOM_SYNC_STATS" ] && [ "$FANTOM_SYNC_STATS" != "false" ]; then
     FANTOM_SYNC_BLOCK=$(su bcuser -c '/home/bcuser/go-opera/build/opera attach --datadir=/data --exec "ftm.syncing.currentBlock"')
     FANTOM_HIGHEST_BLOCK=$(su bcuser -c '/home/bcuser/go-opera/build/opera attach --datadir=/data --exec "ftm.syncing.highestBlock"')
-    
+
     FANTOM_BLOCKS_BEHIND="$((FANTOM_HIGHEST_BLOCK-FANTOM_SYNC_BLOCK))"
 
 else
diff --git a/lib/scroll/README.md b/lib/scroll/README.md
@@ -76,7 +76,7 @@ This is the Well-Architected checklist for Ethereum nodes implementation of the
 
 ### Open AWS CloudShell
 
-To begin, ensure you login to your AWS account with permissions to create and modify resources in IAM, EC2, EBS, VPC, S3, KMS, and Secrets Manager. 
+To begin, ensure you login to your AWS account with permissions to create and modify resources in IAM, EC2, EBS, VPC, S3, KMS, and Secrets Manager.
 
 From the AWS Management Console, open the [AWS CloudShell](https://docs.aws.amazon.com/cloudshell/latest/userguide/welcome.html), a web-based shell environment. If unfamiliar, review the [2-minute YouTube video](https://youtu.be/fz4rbjRaiQM) for an overview and check out [CloudShell with VPC environment](https://docs.aws.amazon.com/cloudshell/latest/userguide/creating-vpc-environment.html) that we'll use to test nodes API from internal IP address space.
 
diff --git a/lib/solana/README.md b/lib/solana/README.md
@@ -93,7 +93,7 @@ This is the Well-Architected checklist for Solana nodes implementation of the AW
 
 ### Open AWS CloudShell
 
-To begin, ensure you login to your AWS account with permissions to create and modify resources in IAM, EC2, EBS, VPC, S3, KMS, and Secrets Manager. 
+To begin, ensure you login to your AWS account with permissions to create and modify resources in IAM, EC2, EBS, VPC, S3, KMS, and Secrets Manager.
 
 From the AWS Management Console, open the [AWS CloudShell](https://docs.aws.amazon.com/cloudshell/latest/userguide/welcome.html), a web-based shell environment. If unfamiliar, review the [2-minute YouTube video](https://youtu.be/fz4rbjRaiQM) for an overview and check out [CloudShell with VPC environment](https://docs.aws.amazon.com/cloudshell/latest/userguide/creating-vpc-environment.html) that we'll use to test nodes API from internal IP address space.
 
diff --git a/lib/stacks/README.md b/lib/stacks/README.md
@@ -70,7 +70,7 @@ This is the Well-Architected checklist for Stacks nodes implementation of the AW
 
 ### Open AWS CloudShell
 
-To begin, ensure you login to your AWS account with permissions to create and modify resources in IAM, EC2, EBS, VPC, S3, KMS, and Secrets Manager. 
+To begin, ensure you login to your AWS account with permissions to create and modify resources in IAM, EC2, EBS, VPC, S3, KMS, and Secrets Manager.
 
 From the AWS Management Console, open the [AWS CloudShell](https://docs.aws.amazon.com/cloudshell/latest/userguide/welcome.html), a web-based shell environment. If unfamiliar, review the [2-minute YouTube video](https://youtu.be/fz4rbjRaiQM) for an overview and check out [CloudShell with VPC environment](https://docs.aws.amazon.com/cloudshell/latest/userguide/creating-vpc-environment.html) that we'll use to test nodes API from internal IP address space.
 
@@ -195,7 +195,7 @@ npx cdk deploy stacks-ha-nodes --json --outputs-file ha-nodes-deploy.json
 export RPC_ABL_URL=$(cat ha-nodes-deploy.json | jq -r '..|.alburl? | select(. != null)')
 echo RPC_ALB_URL=$RPC_ALB_URL
 ```
-   
+
 ```bash
 # IMPORTANT: Run from CloudShell VPC environment tab
 curl http://$RPC_ABL_URL:20443/v2/info' | jq
diff --git a/lib/starknet/README.md b/lib/starknet/README.md
@@ -65,7 +65,7 @@ This is the Well-Architected checklist for Stacks nodes implementation of the AW
 
 ### Open AWS CloudShell
 
-To begin, ensure you login to your AWS account with permissions to create and modify resources in IAM, EC2, EBS, VPC, S3, KMS, and Secrets Manager. 
+To begin, ensure you login to your AWS account with permissions to create and modify resources in IAM, EC2, EBS, VPC, S3, KMS, and Secrets Manager.
 
 From the AWS Management Console, open the [AWS CloudShell](https://docs.aws.amazon.com/cloudshell/latest/userguide/welcome.html), a web-based shell environment. If unfamiliar, review the [2-minute YouTube video](https://youtu.be/fz4rbjRaiQM) for an overview and check out [CloudShell with VPC environment](https://docs.aws.amazon.com/cloudshell/latest/userguide/creating-vpc-environment.html) that we'll use to test nodes API from internal IP address space.
 
diff --git a/lib/sui/README.md b/lib/sui/README.md
@@ -18,7 +18,7 @@ This setup is for PoC or development environments and it supports Devnet, Testne
 
 ### Open AWS CloudShell
 
-To begin, ensure you login to your AWS account with permissions to create and modify resources in IAM, EC2, EBS, VPC, S3, KMS, and Secrets Manager. 
+To begin, ensure you login to your AWS account with permissions to create and modify resources in IAM, EC2, EBS, VPC, S3, KMS, and Secrets Manager.
 
 From the AWS Management Console, open the [AWS CloudShell](https://docs.aws.amazon.com/cloudshell/latest/userguide/welcome.html), a web-based shell environment. If unfamiliar, review the [2-minute YouTube video](https://youtu.be/fz4rbjRaiQM) for an overview and check out [CloudShell with VPC environment](https://docs.aws.amazon.com/cloudshell/latest/userguide/creating-vpc-environment.html) that we'll use to test nodes API from internal IP address space.
 
@@ -228,4 +228,4 @@ curl --location --request POST 'https://fullnode.<Network_ID>.sui.io:443/' --hea
 
 ```
 Enter your node's external IP at https://node.sui.zvalid.com/
-```
+```
diff --git a/lib/sui/lib/constructs/sui-node-security-group.ts b/lib/sui/lib/constructs/sui-node-security-group.ts
@@ -44,6 +44,6 @@ export class SuiNodeSecurityGroupConstruct extends cdkConstructs.Construct {
       ],
       true
     );
-    
+
   }
 }
diff --git a/lib/tezos/.gitignore b/lib/tezos/.gitignore
@@ -6,4 +6,4 @@ node_modules
 # CDK asset staging directory
 .cdk.staging
 cdk.out
-package-lock.json
+package-lock.json
diff --git a/lib/tezos/README.md b/lib/tezos/README.md
@@ -26,7 +26,7 @@ This setup is for small scale PoC or development environments. It deploys a sing
 
 ### Open AWS CloudShell
 
-To begin, ensure you login to your AWS account with permissions to create and modify resources in IAM, EC2, EBS, VPC, S3, KMS, and Secrets Manager. 
+To begin, ensure you login to your AWS account with permissions to create and modify resources in IAM, EC2, EBS, VPC, S3, KMS, and Secrets Manager.
 
 From the AWS Management Console, open the [AWS CloudShell](https://docs.aws.amazon.com/cloudshell/latest/userguide/welcome.html), a web-based shell environment. If unfamiliar, review the [2-minute YouTube video](https://youtu.be/fz4rbjRaiQM) for an overview and check out [CloudShell with VPC environment](https://docs.aws.amazon.com/cloudshell/latest/userguide/creating-vpc-environment.html) that we'll use to test nodes API from internal IP address space.
 
@@ -88,7 +88,7 @@ npx cdk deploy tz-single-node --json --outputs-file single-node-deploy.json
 ```
 > **NOTE:** *The default VPC must have at least two public subnets in different Availability Zones, and public subnet must set `Auto-assign public IPv4 address` to `YES`.*
 
-   The EC2 instance will deploy, initialize the node and start the first sync. In Cloudformation the instance will show as successful once the node is running. From that point it still takes a while until the node is synced to the blockchain. You can check the sync status with the REST call below in step 4. If the `curl cannot connect to the node on port 8732, then the node is still importing. Once that's done, the curl command works. 
+   The EC2 instance will deploy, initialize the node and start the first sync. In Cloudformation the instance will show as successful once the node is running. From that point it still takes a while until the node is synced to the blockchain. You can check the sync status with the REST call below in step 4. If the `curl cannot connect to the node on port 8732, then the node is still importing. Once that's done, the curl command works.
 
 2. After starting the node you need to wait for the inital syncronization process to finish. It may take from an hour to half a day depending on the the state of the network. You can use Amazon CloudWatch to track the progress. To see them:
 
@@ -247,4 +247,4 @@ echo "INSTANCE_ID=" $INSTANCE_ID
 aws ssm start-session --target $INSTANCE_ID --region $AWS_REGION
 sudo su bcuser
 sudo journalctl -o cat -fu s3-sync
-```
+```
diff --git a/lib/tezos/lib/assets/copy-data-to-s3.sh b/lib/tezos/lib/assets/copy-data-to-s3.sh
@@ -9,4 +9,4 @@ s5cmd sync /data/ s3://$S3_SYNC_BUCKET/node/
 
 echo "Synced node to S3"
 
-systemctl start node.service
+systemctl start node.service
diff --git a/lib/tezos/lib/ha-nodes-stack.ts b/lib/tezos/lib/ha-nodes-stack.ts
@@ -20,7 +20,7 @@ export interface TzHANodesStackProps extends cdk.StackProps {
     tzNetwork: configTypes.TzNetwork;
     historyMode: configTypes.TzNodeHistoryMode;
     downloadSnapshot: boolean;
-    octezDownloadUri: string; 
+    octezDownloadUri: string;
     snapshotsUrl: string;
     dataVolume: configTypes.TzDataVolumeConfig;
     albHealthCheckGracePeriodMin: number;
diff --git a/lib/tezos/lib/snapshot-node-stack.ts b/lib/tezos/lib/snapshot-node-stack.ts
@@ -124,7 +124,7 @@ export class TzSnapshotNodeStack extends cdk.Stack {
                 subnetType: ec2.SubnetType.PUBLIC,
             },
         });
-        
+
         // Parsing user data script and injecting necessary variables
         const userData = fs.readFileSync(path.join(__dirname, "assets", "user-data", "node.sh")).toString();
         const modifiedUserData = cdk.Fn.sub(userData, {
@@ -143,22 +143,22 @@ export class TzSnapshotNodeStack extends cdk.Stack {
             _INSTANCE_TYPE_: "SNAPSHOT",
             _S3_SYNC_BUCKET_: snapshotsBucket.bucketName,
         });
-        
+
         // Adding modified userdata script to the instance prepared fro us by Single Node constract
         node.instance.addUserData(modifiedUserData);
-        
+
         // Adding CloudWatch dashboard to the node
         const dashboardString = cdk.Fn.sub(JSON.stringify(nodeCwDashboard.SyncNodeCWDashboardJSON), {
             INSTANCE_ID:node.instanceId,
             INSTANCE_NAME: STACK_NAME,
             REGION: REGION,
         })
-        
+
         new cw.CfnDashboard(this, 'sync-cw-dashboard', {
             dashboardName: `${STACK_NAME}-${node.instanceId}`,
             dashboardBody: dashboardString,
         });
-        
+
         new cdk.CfnOutput(this, "sync-instance-id", {
             value: node.instanceId,
         });
diff --git a/lib/theta/README.md b/lib/theta/README.md
@@ -59,7 +59,7 @@ This is the Well-Architected checklist for Edge nodes implementation of the AWS
 
 ### Open AWS CloudShell
 
-To begin, ensure you login to your AWS account with permissions to create and modify resources in IAM, EC2, EBS, VPC, S3, KMS, and Secrets Manager. 
+To begin, ensure you login to your AWS account with permissions to create and modify resources in IAM, EC2, EBS, VPC, S3, KMS, and Secrets Manager.
 
 From the AWS Management Console, open the [AWS CloudShell](https://docs.aws.amazon.com/cloudshell/latest/userguide/welcome.html), a web-based shell environment. If unfamiliar, review the [2-minute YouTube video](https://youtu.be/fz4rbjRaiQM) for an overview and check out [CloudShell with VPC environment](https://docs.aws.amazon.com/cloudshell/latest/userguide/creating-vpc-environment.html) that we'll use to test nodes API from internal IP address space.
 
