Move tests

.github/workflows/build-php-images.yml

@@ -0,0 +1,127 @@
+name: Build PHP Images
+
+on:
+  # Uncomment below for testing purposes
+  pull_request:
+  push:
+   branches:
+     - main
+
+jobs:
+  buildx:
+    runs-on: ubuntu-20.04
+    env:
+      TERM: xterm
+    strategy:
+      matrix:
+        include:
+          - image: php
+            tag: 8.1-fpm-4
+            context: images/8.1-fpm
+          - image: php
+            tag: 8.1-apache-4
+            context: images/8.1-apache
+          - image: php
+            tag: 8.0-fpm-4
+            context: images/8.0-fpm
+          - image: php
+            tag: 8.0-apache-4
+            context: images/8.0-apache
+          - image: php
+            tag: 7.4-fpm-4
+            context: images/7.4-fpm
+          - image: php
+            tag: 7.4-apache-4
+            context: images/7.4-apache
+          - image: php
+            tag: 7.3-fpm-4
+            context: images/7.3-fpm
+          - image: php
+            tag: 7.3-apache-4
+            context: images/7.3-apache
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v2
+      - name: Set up QEMU
+        uses: docker/setup-qemu-action@v1
+      - name: Set up Docker Buildx
+        id: buildx
+        uses: docker/setup-buildx-action@v1
+        with:
+          install: true
+      - name: Available platforms
+        run: echo ${{ steps.buildx.outputs.platforms }}
+      # Sets our edge tag if on PR.
+      - name: Set tag suffix
+        id: pr
+        if: ${{ github.event_name == 'pull_request' }}
+        run: echo "::set-output name=TAG_SUFFIX::-edge"
+      # Build our images.
+      - name: Login to DockerHub
+        uses: docker/login-action@v1
+        with:
+          username: ${{ secrets.DOCKERHUB_USERNAME }}
+          password: ${{ secrets.DOCKERHUB_TOKEN }}
+      - name: Build and push devwithlando/${{ matrix.image }}:${{ matrix.tag }}${{ steps.pr.outputs.TAG_SUFFIX }}
+        uses: docker/build-push-action@v2
+        with:
+          context: ${{ matrix.context }}
+          platforms: linux/amd64,linux/arm64
+          push: true
+          tags: devwithlando/${{ matrix.image }}:${{ matrix.tag }}${{ steps.pr.outputs.TAG_SUFFIX }}
+
+      # Handle Lando Install to test the images after build
+      # We are hardcoding the dtaa normally included in the matrix 
+      # due to how this testing is setup
+      - name: Install node 14
+        uses: actions/setup-node@v2
+        with:
+          node-version: '14'
+      - name: Get Yarn cache directory
+        id: yarn-cache-dir-path
+        run: echo "::set-output name=dir::$(yarn cache dir)"
+      - name: Use Yarn cache
+        uses: actions/cache@v2
+        id: yarn-cache
+        with:
+          path: ${{ steps.yarn-cache-dir-path.outputs.dir }}
+          key: ubuntu-20.04-yarn-14-${{ hashFiles('**/yarn.lock') }}
+      - name: Install Yarn dependencies
+        run: yarn install --prefer-offline --frozen-lockfile
+      - name: Grab latest edge Lando CLI
+        run: |
+          sudo curl -fsSL -o /usr/local/bin/lando "https://files.lando.dev/cli/lando-linux-x64-edge"
+          sudo chmod +x /usr/local/bin/lando
+      - name: Move in lando config appropriate for testing
+        run: |
+          mkdir -p ~/.lando/cache
+          cp -f actions-lando-config.yml ~/.lando/config.yml
+          echo false > ~/.lando/cache/report_errors
+          lando --clear
+      - name: Verify Lando works and we are dogfooding this plugin for tests
+        run: |
+          lando version
+          lando config --path plugins | grep php | grep /home/runner/work/php/php || echo "::error:: Not dogfooding this plugin correctly! "
+      # This block should eventually become use lando/actions-leia@v2
+      # @NOTE? Do we want a way for our leia-action to configure apparmor since
+      # this might break a whole bunch of tests? or is this literally just a thing
+      # for the Lagoon mysql/mariadb container?
+      - name: Configure apparmor
+        run: |
+          set -x
+          sudo apt-get remove mysql-server --purge
+          sudo apt-get install apparmor-profiles
+          sudo apparmor_parser -R /etc/apparmor.d/usr.sbin.mysqld
+
+      # Test newly built images.
+      - name: Test Edge Images on PR
+        if: ${{ github.event_name == 'pull_request' }}
+        shell: bash
+        run: |
+          yarn leia "./examples/images-edge/${{ matrix.tag }}/README.md" -c 'Destroy tests' --stdin --shell bash
+      - name: Test Stable Images on Push
+        if: ${{ github.event_name == 'push' }}
+        shell: bash
+        run: |
+          yarn leia "./examples/images-stable/${{ matrix.tag }}/README.md" -c 'Destroy tests' --stdin --shell bash

.github/workflows/pr-legacy-php5-tests.yml

@@ -0,0 +1,79 @@
+name: Legacy PHP 5 Tests
+
+on:
+  pull_request:
+
+jobs:
+  leia-tests:
+    runs-on: ${{ matrix.os }}
+    env:
+      TERM: xterm
+    strategy:
+      matrix:
+        leia-tests:
+          - examples/5.3
+          - examples/5.4
+          - examples/5.5
+          - examples/5.6
+        lando-versions:
+          - edge
+        os:
+          - ubuntu-20.04
+        node-version:
+          - '14'
+    steps:
+      # Install deps and cache
+      # Eventually it would be great if these steps could live in a separate YAML file
+      # that could be included in line to avoid code duplication
+      - name: Checkout code
+        uses: actions/checkout@v2
+      - name: Install node ${{ matrix.node-version }}
+        uses: actions/setup-node@v2
+        with:
+          node-version: ${{ matrix.node-version }}
+      - name: Get Yarn cache directory
+        id: yarn-cache-dir-path
+        run: echo "::set-output name=dir::$(yarn cache dir)"
+      - name: Use Yarn cache
+        uses: actions/cache@v2
+        id: yarn-cache
+        with:
+          path: ${{ steps.yarn-cache-dir-path.outputs.dir }}
+          key: ${{ runner.os }}-yarn-${{ matrix.node-version }}-${{ hashFiles('**/yarn.lock') }}
+      - name: Install Yarn dependencies
+        run: yarn install --prefer-offline --frozen-lockfile
+
+      # This block should eventually become use lando/actions-hyperdrive@v2
+      - name: Verify Docker dependencies
+        run: |
+          docker --version | grep "20.10."
+          docker-compose --version | grep "1.29."
+      - name: Grab latest edge Lando CLI
+        run: |
+          sudo curl -fsSL -o /usr/local/bin/lando "https://files.lando.dev/cli/lando-linux-x64-${{ matrix.lando-versions }}"
+          sudo chmod +x /usr/local/bin/lando
+      - name: Move in lando config appropriate for testing
+        run: |
+          mkdir -p ~/.lando/cache
+          cp -f actions-lando-config.yml ~/.lando/config.yml
+          echo false > ~/.lando/cache/report_errors
+          lando --clear
+      - name: Verify Lando works and we are dogfooding this plugin for tests
+        run: |
+          lando version
+          lando config --path plugins | grep php | grep /home/runner/work/php/php || echo "::error:: Not dogfooding this plugin correctly! "
+
+      # This block should eventually become use lando/actions-leia@v2
+      # @NOTE? Do we want a way for our leia-action to configure apparmor since
+      # this might break a whole bunch of tests? or is this literally just a thing
+      # for the Lagoon mysql/mariadb container?
+      - name: Configure apparmor
+        run: |
+          set -x
+          sudo apt-get remove mysql-server --purge
+          sudo apt-get install apparmor-profiles
+          sudo apparmor_parser -R /etc/apparmor.d/usr.sbin.mysqld
+
+      - name: Run leia tests
+        shell: bash
+        run: yarn leia "./${{ matrix.leia-tests }}/README.md" -c 'Destroy tests' --stdin --shell bash

.github/workflows/pr-legacy-php7-tests.yml

@@ -0,0 +1,77 @@
+name: Legacy PHP 7 Tests
+
+on:
+  pull_request:
+
+jobs:
+  leia-tests:
+    runs-on: ${{ matrix.os }}
+    env:
+      TERM: xterm
+    strategy:
+      matrix:
+        leia-tests:
+          - examples/7.0
+          - examples/7.1
+          - examples/7.2
+        lando-versions:
+          - edge
+        os:
+          - ubuntu-20.04
+        node-version:
+          - '14'
+    steps:
+      # Install deps and cache
+      # Eventually it would be great if these steps could live in a separate YAML file
+      # that could be included in line to avoid code duplication
+      - name: Checkout code
+        uses: actions/checkout@v2
+      - name: Install node ${{ matrix.node-version }}
+        uses: actions/setup-node@v2
+        with:
+          node-version: ${{ matrix.node-version }}
+      - name: Get Yarn cache directory
+        id: yarn-cache-dir-path
+        run: echo "::set-output name=dir::$(yarn cache dir)"
+      - name: Use Yarn cache
+        uses: actions/cache@v2
+        id: yarn-cache
+        with:
+          path: ${{ steps.yarn-cache-dir-path.outputs.dir }}
+          key: ${{ runner.os }}-yarn-${{ matrix.node-version }}-${{ hashFiles('**/yarn.lock') }}
+      - name: Install Yarn dependencies
+        run: yarn install --prefer-offline --frozen-lockfile
+
+      # This block should eventually become use lando/actions-hyperdrive@v2
+      - name: Verify Docker dependencies
+        run: |
+          docker --version | grep "20.10."
+          docker-compose --version | grep "1.29."
+      - name: Grab latest edge Lando CLI
+        run: |
+          sudo curl -fsSL -o /usr/local/bin/lando "https://files.lando.dev/cli/lando-linux-x64-${{ matrix.lando-versions }}"
+          sudo chmod +x /usr/local/bin/lando
+      - name: Move in lando config appropriate for testing
+        run: |
+          mkdir -p ~/.lando/cache
+          cp -f actions-lando-config.yml ~/.lando/config.yml
+          echo false > ~/.lando/cache/report_errors
+          lando --clear
+      - name: Verify Lando works and we are dogfooding this plugin for tests
+        run: |
+          lando version
+          lando config --path plugins | grep php | grep /home/runner/work/php/php || echo "::error:: Not dogfooding this plugin correctly! "
+
+      # This block should eventually become use lando/actions-leia@v2
+      # @NOTE? Do we want a way for our leia-action to configure apparmor since
+      # this might break a whole bunch of tests? or is this literally just a thing
+      # for the Lagoon mysql/mariadb container?
+      - name: Configure apparmor
+        run: |
+          set -x
+          sudo apt-get remove mysql-server --purge
+          sudo apt-get install apparmor-profiles
+          sudo apparmor_parser -R /etc/apparmor.d/usr.sbin.mysqld
+      - name: Run leia tests
+        shell: bash
+        run: yarn leia "./${{ matrix.leia-tests }}/README.md" -c 'Destroy tests' --stdin --shell bash

.github/workflows/pr-php-extension-tests.yml

@@ -0,0 +1,76 @@
+name: PHP Extension Tests
+
+on:
+  pull_request:
+
+jobs:
+  leia-tests:
+    runs-on: ${{ matrix.os }}
+    env:
+      TERM: xterm
+    strategy:
+      matrix:
+        leia-tests:
+          - examples/php-extensions
+        lando-versions:
+          - edge
+        os:
+          - ubuntu-20.04
+        node-version:
+          - '14'
+    steps:
+
+      # Install deps and cache
+      # Eventually it would be great if these steps could live in a separate YAML file
+      # that could be included in line to avoid code duplication
+      - name: Checkout code
+        uses: actions/checkout@v2
+      - name: Install node ${{ matrix.node-version }}
+        uses: actions/setup-node@v2
+        with:
+          node-version: ${{ matrix.node-version }}
+      - name: Get Yarn cache directory
+        id: yarn-cache-dir-path
+        run: echo "::set-output name=dir::$(yarn cache dir)"
+      - name: Use Yarn cache
+        uses: actions/cache@v2
+        id: yarn-cache
+        with:
+          path: ${{ steps.yarn-cache-dir-path.outputs.dir }}
+          key: ${{ runner.os }}-yarn-${{ matrix.node-version }}-${{ hashFiles('**/yarn.lock') }}
+      - name: Install Yarn dependencies
+        run: yarn install --prefer-offline --frozen-lockfile
+
+      # This block should eventually become use lando/actions-hyperdrive@v2
+      - name: Verify Docker dependencies
+        run: |
+          docker --version | grep "20.10."
+          docker-compose --version | grep "1.29."
+      - name: Grab latest edge Lando CLI
+        run: |
+          sudo curl -fsSL -o /usr/local/bin/lando "https://files.lando.dev/cli/lando-linux-x64-${{ matrix.lando-versions }}"
+          sudo chmod +x /usr/local/bin/lando
+      - name: Move in lando config appropriate for testing
+        run: |
+          mkdir -p ~/.lando/cache
+          cp -f actions-lando-config.yml ~/.lando/config.yml
+          echo false > ~/.lando/cache/report_errors
+          lando --clear
+      - name: Verify Lando works and we are dogfooding this plugin for tests
+        run: |
+          lando version
+          lando config --path plugins | grep php | grep /home/runner/work/php/php || echo "::error:: Not dogfooding this plugin correctly! "
+
+      # This block should eventually become use lando/actions-leia@v2
+      # @NOTE? Do we want a way for our leia-action to configure apparmor since
+      # this might break a whole bunch of tests? or is this literally just a thing
+      # for the Lagoon mysql/mariadb container?
+      - name: Configure apparmor
+        run: |
+          set -x
+          sudo apt-get remove mysql-server --purge
+          sudo apt-get install apparmor-profiles
+          sudo apparmor_parser -R /etc/apparmor.d/usr.sbin.mysqld
+      - name: Run leia tests
+        shell: bash
+        run: yarn leia "./${{ matrix.leia-tests }}/README.md" -c 'Destroy tests' --stdin --shell bash