Skip to content
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

Expand e2e test coverage to include generating amplify_outputs doesn't break with new version #1918

Open
Amplifiyer opened this issue Aug 26, 2024 · 0 comments
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

Comments

@Amplifiyer
Copy link
Contributor

Amplifiyer commented Aug 26, 2024

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

@Amplifiyer Amplifiyer added 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 amplify_outputs Issue related to generating amplify_outputs for deployed backends generate Issues tied to generate command labels Aug 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

1 participant