fix: Introduce a replace trigger in endpoints change #92
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.
Description
The change introduces a replace trigger to force ls endpoints replacement if we get a new changes in the endpoints config.
Motivation and Context
This fix is a workaround for the issue hashicorp/terraform-provider-aws#35834 in the aws provider which many users are struggling with at the moment. The best is to fix the issue in the terraform aws provider but this could help meanwhile until the issue is picket from aws provider side.
Breaking Changes
No
How Has This Been Tested?
examples/*to demonstrate and validate my change(s)examples/*projectspre-commit run -aon my pull request