Merge branch '3.0.0/auth-refactor' of https://github.com/SarthakJain2…

…6/litmus into 3.0.0/auth-refactor

.gitattributes

@@ -0,0 +1,3 @@
+*.go linguist-language=Go
+*.sh linguist-language=Shell
+*.js linguist-language=JavaScript

.github/BUILD_IMAGE.md

@@ -107,13 +107,13 @@ OR
 
 ```bash
 cd ${DIRECTORY}
-docker buildx build -f Dockerfile --progress plane --push --no-cache --platform ${PLATFORMS} -t ${REPONAME}/$(IMAGE_NAME):$(IMG_TAG} .
+docker buildx build -f Dockerfile --progress plain --push --no-cache --platform ${PLATFORMS} -t ${REPONAME}/$(IMAGE_NAME):$(IMG_TAG} .
 ```
 
 For frontend image:
 
 ```bash
 cd ${DIRECTORY}
-docker buildx build . -f Dockerfile --progress plane --push --no-cache --platform ${PLATFORMS} -t ${REPONAME}/${IMAGE_NAME}:${IMG_TAG} \
+docker buildx build . -f Dockerfile --progress plain --push --no-cache --platform ${PLATFORMS} -t ${REPONAME}/${IMAGE_NAME}:${IMG_TAG} \
 --build-arg REACT_APP_KB_CHAOS_VERSION=${IMG_TAG} --build-arg REACT_APP_BUILD_TIME="${timestamp}" --build-arg REACT_APP_HUB_BRANCH_NAME="v1.13.x"
 ```

.github/workflows/build.yml

@@ -58,7 +58,8 @@ jobs:
         uses: Jerome1337/[email protected]
         with:
           goimports-path: ./litmus-portal
-      - shell: bash
+      - name: Backend checks
+        shell: bash
         run: |
           cd litmus-portal
           make backend-services-checks
@@ -79,11 +80,29 @@ jobs:
           cd litmus-portal
           make frontend-services-checks
 
+  backend-unit-tests:
+    runs-on: ubuntu-latest
+    needs:
+      - changes
+      - backend-checks
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v2
+      - uses: actions/setup-go@v2
+        with:
+          go-version: "1.16" # By default, the go version is v1.15 in runner.
+      - name: Backend unit tests
+        shell: bash
+        run: |
+          cd litmus-portal
+          make unit-tests
+
   docker-build-graphql-server:
     runs-on: ubuntu-latest
     needs:
       - backend-checks
       - changes
+      - backend-unit-tests
     if: ${{ needs.changes.outputs.graphql-server == 'true' }}
     steps:
       - name: Checkout code
@@ -99,7 +118,7 @@ jobs:
         with:
           image-ref: 'docker.io/litmuschaos/litmusportal-server:${{ github.sha }}'
           format: 'table'
-          exit-code: '1'
+          exit-code: '0'
           ignore-unfixed: true
           vuln-type: 'os,library'
           severity: 'CRITICAL,HIGH'          
@@ -109,6 +128,7 @@ jobs:
     needs:
       - backend-checks
       - changes
+      - backend-unit-tests
     if: ${{ needs.changes.outputs.authentication == 'true' }}
     steps:
       - name: Checkout code
@@ -133,6 +153,7 @@ jobs:
     needs:
       - backend-checks
       - changes
+      - backend-unit-tests
     if: ${{ needs.changes.outputs.subscriber == 'true' }}
     steps:
       - name: Checkout code
@@ -147,7 +168,7 @@ jobs:
         with:
           image-ref: 'docker.io/litmuschaos/litmusportal-subscriber:${{ github.sha }}'
           format: 'table'
-          exit-code: '1'
+          exit-code: '0'
           ignore-unfixed: true
           vuln-type: 'os,library'
           severity: 'CRITICAL,HIGH'
@@ -157,6 +178,7 @@ jobs:
     needs:
       - backend-checks
       - changes
+      - backend-unit-tests
     if: ${{ needs.changes.outputs.event-tracker == 'true' }}
     steps:
       - name: Checkout code
@@ -181,6 +203,7 @@ jobs:
     needs:
       - backend-checks
       - changes
+      - backend-unit-tests
     if: ${{ needs.changes.outputs.upgrade-agent-cp == 'true' }}
     steps:
       - name: Checkout code
@@ -220,6 +243,7 @@ jobs:
     needs:
       - backend-checks
       - changes
+      - backend-unit-tests
     if: needs.changes.outputs.dex-server == 'true'
     steps:
       - name: Checkout code

ADOPTERS.md

@@ -24,6 +24,7 @@ The companies listed here conform to [CNCF's definition of end-users](https://gi
 |[FIS](https://www.fisglobal.com/en/)|Larger SRE Transformation with Chaos Engineering|[Our Story](adopters/organizations/fis.md)|
 |[Adidas](https://adidas.com/)|Implementing Chaos Engineering as a practice at Adidas|[Our Story](adopters/organizations/adidas.md)|
 |[Cyren](https://www.cyren.com/)|Implementing Chaos Engineering as a practice at Cyren|[Our Story](https://www.infoq.com/articles/chaos-engineering-cloud-native/)|
+|[AB-Inbev](https://www.ab-inbev.com/)|Implementing Chaos Engineering as a practice at AB-Inbev|[Our Story](adopters/organizations/abinbev.md)|
 
 ### Cloud-Native Vendors
 
@@ -41,6 +42,8 @@ devops/reliability pipelines (such as for customer portals/websites etc.,) withi
 |[VMWare](https://www.vmware.com/)|Chaos Engineering in CD|[Our Story](adopters/organizations/vmware.md)|
 |[Zebrium](https://www.zebrium.com?utm_source=github&utm_campaign=litmuschaos_repo)|[Zebrium K8s Chaos Project](https://github.com/zebrium/zebrium-kubernetes-demo)|[Our Story](adopters/organizations/zebrium.md)|
 |[Container Solutions](https://www.container-solutions.com/)|Building Chaos Engineering for E-Commerce Customers|[Our Story](adopters/organizations/containersolutions.md)|
+|[Infracloud Technologies](https://www.infracloud.io/)|Developing Resiliency Framework at Infracloud|[Our Story](adopters/organizations/infracloud.md)|
+
 
 ### Cloud-Native Solutions & Service Providers
 
@@ -53,6 +56,8 @@ They use LitmusChaos as the tool of choice for carrying out chaos experiments in
 | [Neudesic](https://www.neudesic.com/) | Chaos Engineering | [Our Story](adopters/organizations/neudesic.md) |
 |[WeScale](https://www.wescale.fr)|[Chaos Engineering](https://blog.wescale.fr/2020/03/19/le-guide-de-chaos-engineering-partie-2/)|[Our Story](adopters/organizations/wescale.md)|
 |[Wipro](https://www.wipro.com/en-IN/infrastructure/wipros-appanywhere/?utm_source=github&utm_campaign=litmuschaos_repo)|[Wipro AppAnywhere](https://www.wipro.com/en-IN/infrastructure/wipros-appanywhere/?utm_source=github&utm_campaign=litmuschaos_repo)|[Our Story](adopters/organizations/wipro.md)|
+|[HCL Cloud Native Labs](https://www.hcltech.com/)|SRE Enablement Service|[Our Story(TBA)]|
+|[CI&T](https://ciandt.com/us/en-us)|Chaos Engineering Implementation|[Our Story](adopters/organizations/ci&t.md)|
 
 ### Cloud-Native OSS Projects 
 
@@ -69,5 +74,6 @@ existing functions.
 |[Red Hat](https://www.redhat.com/en)|[Chaos Engineering with Kraken](https://github.com/cloud-bulldozer/kraken)|[Our Story](adopters/organizations/redhat_kraken.md)|
 |[Iter8](https://iter8.tools)|[SLO validation with chaos injection](https://iter8.tools/0.7/tutorials/deployments/slo-validation-chaos/)|To Be Added|
 |[CNF Test Suite](https://github.com/cncf/cnf-testsuite)|To validate the resilience of Cloud Native Network Functions (CNFs)|[Our Story](adopters/organizations/cnftestsuite.md)|
+|[APACHE APISIX](https://apisix.apache.org/)|Practicing Chaos Engineering using Litmus in the Apache APISIX Ingress.|[Our Story](adopters/organizations/apisix.md)|