Expand e2e test coverage to include generating amplify_outputs doesn't break with new version #1918
Labels
amplify_outputs
Issue related to generating amplify_outputs for deployed backends
generate
Issues tied to generate command
tech-debt
Refactors, unsavory workarounds or other technical decisions that should be revisited later
testing
Engineering label for issues related to tests or test tooling
Description
we should expand this amplify_outputs test to cover programmatic read of outputs.
It would prevent us from launching breaking backwards incompatible changes. (See example here where we assert that old version can be read by new).
Reference PR that brought this to attention: #1917 and issue #1914
The text was updated successfully, but these errors were encountered: