-
Notifications
You must be signed in to change notification settings - Fork 4.3k
fix(bedrock-alpha): added missing validation when prompt uses default variant #35366
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(This review is outdated)
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Comments on closed issues and PRs are hard for our team to see. |
Issue # (if applicable)
Closes #.
Reason for this change
When using Prompts and PromptVariants in bedrock, you can define the default variant your prompt will use, but if you dont add it to the variants array too, it will fail at deployment time.
Description of changes
Added a validation that checks the correct conditions at synth time, so you don't waste time and leave a stack with a bad deployment
Describe any new or updated permissions being added
NA
Description of how you validated changes
Unit tests. We don't create integ tests for validations (synth time) as they wont add any additional value
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license