add warning about future deprecation of stepfunctions v1 provider #9198
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Sep 21, 2023
giograno
approved these changes
Sep 25, 2023
4814885 to
f8fb908
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
v2stepfunctions provider more broadly and also let users know that with the next major release, the defaults will change. Ideally anyone using stepfunctions should start to at least opt-in at some point and make sure their current applications are still working withv2.v1) provider will become deprecated andv2will become the new default. Users can still opt-in to the oldv1provider.v1) provider will be removed completely.Changes
v1provider is used. Only logged during initialization since a lot of people might not be affected at this point if they're not using the stepfunctions service at all.Discussion
We should also make sure our language is somewhat similar between all the upcoming provider deprecations (s3, lambda, stepfunctions). /cc @bentsku @joe4dev