generated from amazon-archives/__template_Apache-2.0
-
Notifications
You must be signed in to change notification settings - Fork 174
Closed
Labels
automationThis item relates to automationThis item relates to automationconfirmedThe scope is clear, ready for implementationThe scope is clear, ready for implementationinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Description
Summary
In a recent PR we modified the way in which the packages in the workspace are installed and built. In doing so I forgot to update one of the workflows that is in charge of running the integration tests, which due to this misconfiguration now fails consistently.
Why is this needed?
So that we are able to run the integration tests in our CI.
Which area does this relate to?
Automation, Tests
Solution
No response
Acknowledgment
- This request meets Powertools for AWS Lambda (TypeScript) Tenets
- Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET
Future readers
Please react with 👍 and your use case to help us understand customer demand.
Metadata
Metadata
Assignees
Labels
automationThis item relates to automationThis item relates to automationconfirmedThe scope is clear, ready for implementationThe scope is clear, ready for implementationinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Type
Projects
Status
Shipped