Skip to content

Commit

Permalink
Release v3.1.0 into Main
Browse files Browse the repository at this point in the history
  • Loading branch information
estohlmann authored Oct 14, 2024
2 parents cc0975a + 46bc339 commit 611954b
Show file tree
Hide file tree
Showing 65 changed files with 2,340 additions and 1,091 deletions.
1 change: 1 addition & 0 deletions .github/workflows/code.hotfix.branch.yml
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,7 @@ jobs:
DST_TAG=${{ github.event.inputs.dest_tag }}
git checkout -b hotfix/${{ github.event.inputs.dest_tag }}
sed -i -e "s/\"version\": \"${SRC_TAG:1}\"/\"version\": \"${DST_TAG:1}\"/g" package.json
sed -i -e "s/\"version\": \"${SRC_TAG:1}\"/\"version\": \"${DST_TAG:1}\"/g" lib/user-interface/react/package.json
sed -i -e "s/version = \"${SRC_TAG:1}\"/version = \"${DST_TAG:1}\"/g" lisa-sdk/pyproject.toml
sed -i -e "s/${SRC_TAG:1}/${DST_TAG:1}/g" VERSION
git commit -a -m "Updating version for hotfix ${{ github.event.inputs.dest_tag }}"
Expand Down
6 changes: 2 additions & 4 deletions .github/workflows/code.merge.main-to-develop.yml
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,6 @@ on:
types: [released]

permissions:
id-token: write
contents: write

jobs:
Expand All @@ -16,17 +15,16 @@ jobs:
uses: actions/checkout@v4
with:
ref: main
ssh-key: ${{ secrets.DEPLOYMENT_SSH_KEY }}
- name: merge main into develop
run: |
git config --global user.email "[email protected]"
git config --global user.name "github_actions_lisa"
git fetch --unshallow
git checkout develop
git pull
git merge --no-ff origin/main -m "Auto-merge main back to dev post release"
git merge --no-ff origin/main -m "Auto-merge main back to develop post release"
git push --force origin develop
env:
GH_TOKEN: ${{ secrets.LEAD_ACCESS_TOKEN }}
send_final_slack_notification:
name: Send Final Slack Notification
needs: [conduct_merge]
Expand Down
1 change: 1 addition & 0 deletions .github/workflows/code.release.branch.yml
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,7 @@ jobs:
git config --global user.name "github_actions_lisa"
RELEASE_TAG=${{ github.event.inputs.release_tag }}
git checkout -b release/${{ github.event.inputs.release_tag }}
echo "$( jq --arg version ${RELEASE_TAG:1} '.version = $version' lib/user-interface/react/package.json )" > lib/user-interface/react/package.json
echo "$( jq --arg version ${RELEASE_TAG:1} '.version = $version' package.json )" > package.json
sed -E -i -e "s/version = \"[0-9\.].+\"/version = \"${RELEASE_TAG:1}\"/g" lisa-sdk/pyproject.toml
echo ${RELEASE_TAG:1} > VERSION
Expand Down
30 changes: 30 additions & 0 deletions .github/workflows/issues.alert.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
name: Alert on Issue Creation
on:
issues:
types: [opened, reopened]

jobs:
send_slack_notification:
name: Send Issue Alert Slack Notification
runs-on: ubuntu-latest
steps:
- name: Send slack notification for issue created
uses: rtCamp/action-slack-notify@v2
if: github.event.action == 'opened'
env:
SLACK_WEBHOOK: ${{ secrets.INTERNAL_DEV_SLACK_WEBHOOK_URL }}
SLACK_COLOR: 'success'
SLACK_TITLE: 'Issue Created'
SLACK_FOOTER: ''
MSG_MINIMAL: 'true'
SLACK_MESSAGE: '<!here> Issue <${{ github.event.issue.html_url }}|${{ github.event.issue.title }}> created by ${{ github.event.sender.login }}'
- name: Send slack notification for issue reopened
uses: rtCamp/action-slack-notify@v2
if: github.event.action == 'reopened'
env:
SLACK_WEBHOOK: ${{ secrets.INTERNAL_DEV_SLACK_WEBHOOK_URL }}
SLACK_COLOR: 'success'
SLACK_TITLE: 'Issue Reopened'
SLACK_FOOTER: ''
MSG_MINIMAL: 'true'
SLACK_MESSAGE: '<!here> Issue <${{ github.event.issue.html_url }}|${{ github.event.issue.title }}> reopened by ${{ github.event.sender.login }}'
30 changes: 30 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,33 @@
# v3.1.0
## Enhancements
### Model Management Administration
- Supports customers updating a subset of model properties through the model management user interface (UI) or APIs
- These new model management features are also limited to users in the configured IDP LISA administration group
- This feature prevents customers from having to delete and re-create models every time they want to make changes to available models already deployed in the infrastructure

### Other Enhancements
- Updated the chat UI to pull available models from the model management APIs instead of LiteLLM. This will allow the UI to pull all metadata that is stored about a model to properly enable/disable features, current model status is used to ensure users can only interact with `InService` models when chatting
- Updated default Model Creation values, so that there are fewer fields that should need updating when creating a model through the UI
- Removed the unnecessary fields for ECS config in the properties file. LISA will be able to go and pull the weights with these optional values and if an internet connection is available
- Added the deployed LISA version in the UI profile dropdown so users understand what version of the software they are using

## Bug fixes
- Updated naming prefixes if they are populated to prevent potential name clashes, customers can now more easily use prefix resource names with LISA
- Fixed an issue where a hard reload was not pulling in the latest models
- Resolved a deployment issue where the SSM deployment parameter was being retained
- Addressed an issue where users could interact with the chat API if a request was being processed by hitting the `Enter` key

## Coming Soon
- Version 3.2.0 will simplify the deployment process by removing all but the key properties required for the deployment, and extracting constants into a separate file as optional items to override. This will make LISA's deployment process a lot easier to understand and manage.

## Acknowledgements
* @petermuller
* @estohlmann
* @dustins

**Full Changelog**: https://github.com/awslabs/LISA/compare/v3.0.1...v3.1.0


# v3.0.1
## Bug fixes
- Updated our Lambda admin validation to work for no-auth if user has the admin secret token. This applies to model management APIs.
Expand Down
4 changes: 2 additions & 2 deletions Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -180,7 +180,7 @@ modelCheck:
echo "What is your huggingface access token? "; \
read -s access_token; \
echo "Converting and uploading safetensors for model: $(MODEL_ID)"; \
tgiImage=$$(yq '[.$(ENV).ecsModels[] | select(.inferenceContainer == "tgi") | .containerConfig.image.baseImage] | first' $(PROJECT_DIR)/config.yaml | sed "s/^['\"]//;s/['\"]$$//"); \
tgiImage=$$(yq -r '[.$(ENV).ecsModels[] | select(.inferenceContainer == "tgi") | .baseImage] | first' $(PROJECT_DIR)/config.yaml); \
echo $$tgiImage; \
$(PROJECT_DIR)/scripts/convert-and-upload-model.sh -m $(MODEL_ID) -s $(MODEL_BUCKET) -a $$access_token -t $$tgiImage -d $$localModelDir; \
fi; \
Expand Down Expand Up @@ -237,7 +237,7 @@ listStacks:
@npx cdk list

buildEcsDeployer:
@cd ./ecs_model_deployer && npm install && npm run build &> /dev/null
@cd ./ecs_model_deployer && npm install && npm run build

## Deploy all infrastructure
deploy: dockerCheck dockerLogin cleanMisc modelCheck buildEcsDeployer
Expand Down
Loading

0 comments on commit 611954b

Please sign in to comment.