feat: merge changes before transferring ownership (#101)

# 🤖 Linear

Closes GIT-XXX

## Description

## Checklist before requesting a review

-   [ ] I have conducted a self-review of my code.
-   [ ] I have conducted a QA.
-   [ ] If it is a core feature, I have included comprehensive tests.


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **New Features**
- Launched an enhanced funding mechanism that streamlines registration
and distribution processes.
- Expanded support for additional networks, offering broader ecosystem
connectivity.
- Introduced a new event type, "DistributionUpdatedWithMerkleRoot,"
enhancing event handling capabilities.
- Added a new handler for managing "RegisteredWithSender" events within
the Easy Retro Funding strategy.
- Updated event handling to accommodate
"DistributionUpdatedWithMerkleRoot" across various components.
- Enhanced the workflow for end-to-end tests, improving testing accuracy
and reliability.

- **Documentation**
- Updated operational and configuration guidelines for clearer setup and
smoother deployments.
- Enhanced clarity in environment variable documentation and workflow
descriptions.

- **Chores**
- Refined deployment workflows and performance settings to improve
overall system reliability.
- Increased default fetch limit for public data access in Hasura
configuration.

- **Tests**
- Strengthened testing coverage to ensure robust event handling and
maintain system stability.
- Added new test cases for the Easy Retro Funding strategy and updated
existing tests for event handling.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: 0xkenj1 <[email protected]>
Co-authored-by: 0xkenj1 <[email protected]>

Author: thelostone-mc

.github/README.md

@@ -4,21 +4,20 @@ This directory contains the GitHub Actions workflows for the Grants Stack Indexe
 
 ## Available Workflows
 
-| Workflow                 | Description                                     |
-| ------------------------ | ----------------------------------------------- |
-| `main-workflow.yml`      | Main CI pipeline triggered on PR to dev/main    |
-| `build.yml`              | Handles project building and type checking      |
-| `build-image.yml`        | Builds and validates Docker images              |
-| `lint.yml`               | Runs code linting and commit message validation |
-| `test.yml`               | Executes unit tests with coverage               |
-| `test-integration.yml`   | Runs integration tests                          |
-| `create-ecr.yml`         | Creates ECR repository in AWS                   |
-| `create-s3.yaml`         | Creates S3 bucket for terraform state           |
-| `deploy-to-aws.yaml`     | First-time deployment to AWS                    |
-| `deploy-blue-green.yml`  | Handles blue-green deployment (Step 1)          |
-| `promote-blue-green.yml` | Promotes blue-green deployment (Step 2)         |
-| `destroy-blue-green.yml` | Finalizes blue-green deployment (Step 3)        |
-| `destroy-deployment.yml` | Destroys environment resources                  |
+| Workflow                 | Description                                       |
+| ------------------------ | ------------------------------------------------- |
+| `main-workflow.yml`      | Main CI pipeline triggered on PR to dev/main      |
+| `build.yml`              | Handles project building and type checking        |
+| `build-image.yml`        | Builds and validates Docker images                |
+| `lint.yml`               | Runs code linting and commit message validation   |
+| `test.yml`               | Executes unit and integration tests with coverage |
+| `create-ecr.yml`         | Creates ECR repository in AWS                     |
+| `create-s3.yaml`         | Creates S3 bucket for terraform state             |
+| `deploy-to-aws.yaml`     | First-time deployment to AWS                      |
+| `deploy-blue-green.yml`  | Handles blue-green deployment (Step 1)            |
+| `promote-blue-green.yml` | Promotes blue-green deployment (Step 2)           |
+| `destroy-blue-green.yml` | Finalizes blue-green deployment (Step 3)          |
+| `destroy-deployment.yml` | Destroys environment resources                    |
 
 ## Main Workflow
 
@@ -93,13 +92,14 @@ Each step requires manual trigger with environment selection (blue/green) to ens
 
 ## Required Configuration
 
-###Environment Variables and Secrets
+### Environment Variables and Secrets
+
 To properly configure your GitHub repository, set up the following environment variables and secrets:
 
 1. Add Repository Secrets
    Navigate to GitHub Repository Settings → Secrets and add:
 
--   `AWS_ACCESS_KEY_ID`
+-   `AWS_ACCESS_KEY`
 -   `AWS_SECRET_ACCESS_KEY`
 -   `ECR_REGISTRY`
 
@@ -249,5 +249,5 @@ The `push-to-ecr.yaml` workflow automatically pushes images to Amazon ECR when c
 Required secrets for ECR:
 
 -   `ECR_REGISTRY`
--   `AWS_ACCESS_KEY_ID`
+-   `AWS_ACCESS_KEY`
 -   `AWS_SECRET_ACCESS_KEY`

.github/production_operations.md

@@ -10,6 +10,7 @@ This guide is for production operations on the Gitcoin Data Layer.
 
 -   Make sure you have already created the S3 bucket and ECR repository. Refer to the [README.md](./README.md) for more information.
 -   Make sure you have already created environment variables and secrets in the repository settings. Refer to the [README.md](./README.md) for more information.
+-   Run `Push Docker Image to ECR` workflow and ensure the latest commit hash is available in the ECR Registry and use that in the TERRAFORM_VARS image tags
 
 ## First Deployment
 
@@ -21,10 +22,10 @@ This guide is for production operations on the Gitcoin Data Layer.
 4. Go to EC2 > Instances > gitcoin-data-layer-production-bastion > Connect > Session Manager > Connect ( IF YOU CAN’T USE `SessionManager` try rebooting the instance)
 5. Once in the terminal run:
 
-    1. sudo su
-    2. cd ~
-    3. git clone https://github.com/defi-wonderland/grants-stack-indexer-v2.git
-    4. cd grants-stack-indexer-v2
+    1. `sudo su`
+    2. `cd ~`
+    3. `git clone https://github.com/gitcoinco/grants-stack-indexer-v2.git`
+    4. `cd grants-stack-indexer-v2`
     5. set env variables for scripts
 
         1. `nano ./scripts/migrations/.env`
@@ -35,11 +36,11 @@ This guide is for production operations on the Gitcoin Data Layer.
             NODE_ENV=production
             ```
 
-    6. chmod +x ./deployment/bastion_scripts/install_dependencies.sh
-    7. ./deployment/bastion_scripts/install_dependencies.sh
-    8. source ~/.bashrc
-    9. pnpm i && pnpm build
-    10. pnpm db:create-databases
+    6. `chmod +x ./deployment/bastion_scripts/install_dependencies.sh`
+    7. `./deployment/bastion_scripts/install_dependencies.sh`
+    8. `source ~/.bashrc`
+    9. `pnpm i && pnpm build`
+    10. `pnpm db:create-databases`
 
     ### Migrate cache: Run 2 times, first green, blue after.
 
@@ -49,19 +50,18 @@ This guide is for production operations on the Gitcoin Data Layer.
         DATABASE_URL=postgres://{{DB_USER}}:{{DB_PASSWORD}}@{{DB_URL}}:5432/GitcoinDatalayerGreen
         DATABASE_SCHEMA=public
         NODE_ENV=production
-
         ```
 
-    2. pnpm db:cache:migrate
-    3. nano ./scripts/migrations/.env
+    2. `pnpm db:cache:migrate`
+    3. `nano ./scripts/migrations/.env`
 
         ```tsx
         DATABASE_URL=postgres://{{DB_USER}}:{{DB_PASSWORD}}@{{DB_URL}}:5432/GitcoinDatalayerBlue
         DATABASE_SCHEMA=public
         NODE_ENV=production
         ```
 
-    4. pnpm db:cache:migrate
+    4. `pnpm db:cache:migrate`
 
     ### Bootstrap Green database
 
@@ -81,8 +81,8 @@ This guide is for production operations on the Gitcoin Data Layer.
 
         ```
 
-    2. pnpm bootstrap:metadata
-    3. pnpm bootstrap:pricing
+    2. `pnpm bootstrap:metadata`
+    3. `pnpm bootstrap:pricing`
 
     ### Migrate processing tables: Run 2 times, first green, blue after.
 
@@ -94,16 +94,16 @@ This guide is for production operations on the Gitcoin Data Layer.
         NODE_ENV=production
         ```
 
-    2. pnpm db:migrate
-    3. nano ./scripts/migrations/.env
+    2. `pnpm db:migrate`
+    3. `nano ./scripts/migrations/.env`
 
         ```tsx
         DATABASE_URL=postgres://{{DB_USER}}:{{DB_PASSWORD}}@{{DB_URL}}:5432/GitcoinDatalayerBlue
         DATABASE_SCHEMA=public
         NODE_ENV=production
         ```
 
-    4. pnpm db:migrate
+    4. `pnpm db:migrate`
 
 ### Configure API
 
@@ -115,7 +115,9 @@ This guide is for production operations on the Gitcoin Data Layer.
     HASURA_SCHEMA=public
     ```
 
-2. pnpm api:configure
+2. `pnpm api:configure`
+
+_Note: If data isn't populated, check your processing task logs on ECS. If there are issues, fix them and then run `Upgrade current deployment` workflow. Avoid using this unless you are adding a new chain or there are errors during the first time deployment._
 
 ## Upgrade using blue deployment
 
@@ -130,11 +132,11 @@ This guide is for production operations on the Gitcoin Data Layer.
         DATABASE_SCHEMA=public
         NODE_ENV=production
         ```
-    - pnpm db:reset
-    - pnpm db:cache:reset
-    - pnpm db:cache:migrate
-    - pnpm db:copy-cache -f {{ green | blue (should be the source environment) }}
-    - pnpm db:migrate
+    - `pnpm db:reset`
+    - `pnpm db:cache:reset`
+    - `pnpm db:cache:migrate`
+    - `pnpm db:copy-cache -f {{ green | blue (should be the source environment) }}`
+    - `pnpm db:migrate`
     - Set hasura config `nano ./scripts/hasura-config/.env`
 
     ```tsx
@@ -143,7 +145,7 @@ This guide is for production operations on the Gitcoin Data Layer.
         HASURA_SCHEMA=public
     ```
 
-    - pnpm api:configure
+    - `pnpm api:configure`
 
 5. Wait until the new deployment is stable,you can go to the hasura api task on ECS and get the IP address of the task and check if the api is working. (You can rollback running again using `Promote Blue Green (Start upgrade - Step 2)` workflow)
 6. Run `Promote Blue Green (Start upgrade - Step 2)` workflow.