Release v3.2.0 into Main

.github/workflows/code.deploy.demo.yml

@@ -0,0 +1,65 @@
+name: Deploy Demo Environment
+on:
+  push:
+    branches: [ "main"]
+
+permissions:
+  id-token: write
+  contents: read
+
+jobs:
+  CheckPendingWorkflow:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: ahmadnassri/action-workflow-queue@v1
+        with:
+          delay: 300000
+          timeout: 7200000
+  DeployLISA:
+    needs: CheckPendingWorkflow
+    environment: demo
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Configure AWS Credentials
+        uses: aws-actions/configure-aws-credentials@v4
+        with:
+          aws-region: ${{ vars.AWS_REGION }}
+          role-to-assume: arn:aws:iam::${{ vars.AWS_ACCOUNT }}:role/${{ vars.ROLE_NAME_TO_ASSUME }}
+          role-session-name: GitHub_to_AWS_via_FederatedOIDC
+          role-duration-seconds: 14400
+      - name: Create config-custom.yaml
+        id: create-yaml
+        run: |
+          echo "${{vars.CONFIG_YAML}}" > config-custom.yaml
+      - name: Set up Python 3.11
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+      - name: Use Node.js 20.x
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20.x
+      - name: Install CDK dependencies
+        run: |
+          npm install
+      - name: Deploy LISA
+        run: |
+          make deploy HEADLESS=true
+  SendSlackNotification:
+    name: Send Slack Notification
+    needs: [ DeployLISA ]
+    runs-on: ubuntu-latest
+    if: always()
+    steps:
+      - name: Send Notification that Demo Deploy Finished
+        uses: rtCamp/action-slack-notify@v2
+        env:
+          SLACK_WEBHOOK: ${{ secrets.INTERNAL_DEV_SLACK_WEBHOOK_URL }}
+          SLACK_COLOR: ${{ contains(join(needs.*.result, ' '), 'failure') && 'failure' || 'success' }}
+          SLACK_TITLE: 'Demo Deploy Finished'
+          SLACK_FOOTER: ''
+          MSG_MINIMAL: 'actions url,commit'
+          SLACK_MESSAGE_ON_FAILURE: '<!here> Demo Deploy FAILED on branch ${{ github.head_ref || github.ref_name }} for <${{ github.event.pull_request.html_url || github.event.head_commit.url }}|commit>'
+          SLACK_MESSAGE_ON_SUCCESS: 'Demo Deploy SUCCESS on branch ${{ github.head_ref || github.ref_name }} for <${{ github.event.pull_request.html_url || github.event.head_commit.url }}|commit>.'
+          SLACK_MESSAGE: 'Demo Deploy Finished with status ${{ job.status }} on branch ${{ github.head_ref || github.ref_name }} for <${{ github.event.pull_request.html_url || github.event.head_commit.url }}|commit>'

.github/workflows/code.deploy.dev.yml

@@ -0,0 +1,65 @@
+name: Deploy Dev Environment
+on:
+  push:
+    branches: [ "main", "develop", "release/**" ]
+
+permissions:
+  id-token: write
+  contents: read
+
+jobs:
+  CheckPendingWorkflow:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: ahmadnassri/action-workflow-queue@v1
+        with:
+          delay: 300000
+          timeout: 7200000
+  DeployLISA:
+    needs: CheckPendingWorkflow
+    environment: dev
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Configure AWS Credentials
+        uses: aws-actions/configure-aws-credentials@v4
+        with:
+          aws-region: ${{ vars.AWS_REGION }}
+          role-to-assume: arn:aws:iam::${{ vars.AWS_ACCOUNT }}:role/${{ vars.ROLE_NAME_TO_ASSUME }}
+          role-session-name: GitHub_to_AWS_via_FederatedOIDC
+          role-duration-seconds: 14400
+      - name: Create config-custom.yaml
+        id: create-yaml
+        run: |
+          echo "${{vars.CONFIG_YAML}}" > config-custom.yaml
+      - name: Set up Python 3.11
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+      - name: Use Node.js 20.x
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20.x
+      - name: Install CDK dependencies
+        run: |
+          npm install
+      - name: Deploy LISA
+        run: |
+          make deploy HEADLESS=true
+  SendSlackNotification:
+    name: Send Slack Notification
+    needs: [ DeployLISA ]
+    runs-on: ubuntu-latest
+    if: always()
+    steps:
+      - name: Send Notification that Dev Deploy Finished
+        uses: rtCamp/action-slack-notify@v2
+        env:
+          SLACK_WEBHOOK: ${{ secrets.SLACK_WEBHOOK_URL }}
+          SLACK_COLOR: ${{ contains(join(needs.*.result, ' '), 'failure') && 'failure' || 'success' }}
+          SLACK_TITLE: 'Dev Deploy Finished'
+          SLACK_FOOTER: ''
+          MSG_MINIMAL: 'actions url,commit'
+          SLACK_MESSAGE_ON_FAILURE: '<!here> Dev Deploy FAILED on branch ${{ github.head_ref || github.ref_name }} for <${{ github.event.pull_request.html_url || github.event.head_commit.url }}|commit>'
+          SLACK_MESSAGE_ON_SUCCESS: 'Dev Deploy SUCCESS on branch ${{ github.head_ref || github.ref_name }} for <${{ github.event.pull_request.html_url || github.event.head_commit.url }}|commit>.'
+          SLACK_MESSAGE: 'Dev Deploy Finished with status ${{ job.status }} on branch ${{ github.head_ref || github.ref_name }} for <${{ github.event.pull_request.html_url || github.event.head_commit.url }}|commit>'

.github/workflows/code.hotfix.branch.yml

@@ -24,7 +24,7 @@ jobs:
           ref: refs/tags/${{ github.event.inputs.source_tag }}
       - name: Create Hotfix Branch and Update Version
         run: |
-          git config --global user.email "petermul@amazon.com"
+          git config --global user.email "evmann@amazon.com"
           git config --global user.name "github_actions_lisa"
           SRC_TAG=${{ github.event.inputs.source_tag }}
           DST_TAG=${{ github.event.inputs.dest_tag }}

.github/workflows/code.merge.main-to-develop.yml

@@ -18,7 +18,7 @@ jobs:
           ssh-key: ${{ secrets.DEPLOYMENT_SSH_KEY }}
       - name: merge main into develop
         run: |
-          git config --global user.email "petermul@amazon.com"
+          git config --global user.email "evmann@amazon.com"
           git config --global user.name "github_actions_lisa"
           git fetch --unshallow
           git checkout develop

.github/workflows/code.release.branch.yml

@@ -21,7 +21,7 @@ jobs:
           ref: develop
       - name: Create Release Branch and Update Version
         run: |
-          git config --global user.email "petermul@amazon.com"
+          git config --global user.email "evmann@amazon.com"
           git config --global user.name "github_actions_lisa"
           RELEASE_TAG=${{ github.event.inputs.release_tag }}
           git checkout -b release/${{ github.event.inputs.release_tag }}

.github/workflows/docs.deploy.github-pages.yml

@@ -0,0 +1,60 @@
+
+name: Deploy VitePress site to Github Pages
+on:
+  push:
+    branches: [main]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: pages
+  cancel-in-progress: false
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          cache: npm
+      - name: Setup Pages
+        uses: actions/configure-pages@v4
+      - name: Install root dependencies
+        run: |
+          npm install
+      - name: Install dependencies
+        working-directory: ./lib/docs
+        run: npm install
+        env:
+          CI: ""
+      - name: Build with VitePress
+        working-directory: ./lib/docs
+        run: npm run build
+        env:
+          CI: ""
+          DOCS_BASE_PATH: '/LISA/'
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: ./lib/docs/dist
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    needs: build
+    runs-on: ubuntu-latest
+    name: Deploy
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

.github/workflows/test-and-lint.yml

@@ -4,7 +4,7 @@ on:
   push:
     branches: ['main', 'develop', 'release/**', 'hotfix/**']
   pull_request:
-    branches: ['main', 'develop', 'release/**', 'hotfix/**']
+    branches: ['main', 'develop', 'release/**', 'hotfix/**', 'feature/**']
 
 permissions:
   contents: read

.gitignore

@@ -32,3 +32,4 @@ coverage
 /models
 # Deployment configuration file
 config.yaml
+config-custom.yaml

CHANGELOG.md

@@ -1,3 +1,62 @@
+# v3.2.0
+## Key Features
+### Enhanced Deployment Configuration
+- LISA v3.2.0 introduces a significant update to the configuration file schema, optimizing the deployment process
+- The previous single config.yaml file has been replaced with a more flexible two-file system: config-base.yaml and config-custom.yaml
+- config-base.yaml now contains default properties, which can be selectively overridden using config-custom.yaml, allowing for greater customization while maintaining a standardized base configuration
+- The number of required properties in the config-custom.yaml file has been reduced to 8 items, simplifying the configuration process
+- This update enhances the overall flexibility and maintainability of LISA configurations, providing a more robust foundation for future developments and easier customization for end-users
+
+#### Important Note
+- The previous config.yaml file format is no longer compatible with this update
+- To facilitate migration, we have developed a utility. Users can execute `npm run migrate-properties` to automatically convert their existing config.yaml file to the new config-custom.yaml format
+
+### Admin UI Configuration Page
+- Administrative Control of Chat Components:
+  - Administrators now have granular control over the activation and deactivation of chat components for all users through the Configuration Page
+  - This feature allows for dynamic management of user interface elements, enhancing system flexibility and user experience customization
+  - Items that can be configured include:
+    - The option to delete session history
+    - Visibility of message metadata
+    - Configuration of chat Kwargs
+    - Customization of prompt templates
+    - Adjust chat history buffer settings
+    - Modify the number of RAG documents to be included in the retrieval process (TopK)
+    - Ability to upload RAG documents
+    - Ability to upload in-context documents
+- System Banner Management:
+  - The Configuration Page now includes functionality for administrators to manage the system banner
+  - Administrators can activate, deactivate, and update the content of the system banner
+
+### LISA Documentation Site
+- We are pleased to announce the launch of the official [LISA Documentation site](https://awslabs.github.io/LISA/)
+- This comprehensive resource provides customers with additional guides and extensive information on LISA
+- The documentation is also optionally deployable within your environment during LISA deployment
+- The team is continuously working to add and expand content available on this site
+
+## Enhancements
+- Implemented a selection-based interface for instance input, replacing free text entry
+- Improved CDK Nag integration across stacks
+- Added functionality for administrators to specify block volume size for models, enabling successful deployment of larger models
+- Introduced options for administrators to choose between Private or Regional API Gateway endpoints
+- Enabled subnet specification within the designated VPC for deployed resources
+- Implemented support for headless deployment execution
+
+## Bug Fixes
+- Resolved issues with Create and Update model alerts to ensure proper display in the modal
+- Enhanced error handling for model creation/update processes to cover all potential scenarios
+
+## Coming Soon
+- Version 3.3.0 will include a new RAG ingestion pipeline. This will allow users to configure an S3 bucket and an ingestion trigger. When triggered, these documents will be pre-processed and loaded into the selected vector store.
+
+## Acknowledgements
+* @bedanley
+* @estohlmann
+* @dustins
+
+**Full Changelog**: https://github.com/awslabs/LISA/compare/v3.1.0...v3.2.0
+
+
 # v3.1.0
 ## Enhancements
 ### Model Management Administration