Skip to content

Conversation

@vandonr-amz
Copy link
Contributor

@vandonr-amz vandonr-amz commented Apr 21, 2023

this was removed as part of a big PR (#30755) to get rid of all old code that was marked obsolete, but this specific thing is pretty tricky to fix if it breaks customer code.

Also, doing this fallback does not prevent us from moving forward with other things, so I think we should better keep it around, and even not treat it as a deprecated behavior.

@boring-cyborg boring-cyborg bot added area:providers provider:amazon AWS/Amazon - related issues labels Apr 21, 2023
@o-nikolas
Copy link
Contributor

I'm curious to hear what you think of this one @eladkal

If you agree that it's worth merging, I'd like to vote we include this as an RC2 for this amazon provider release.

We rushed in these deprecation changes a bit, and didn't test them as much as we should have.

@eladkal
Copy link
Contributor

eladkal commented Apr 21, 2023

If AWS believes that this part of the code was not suppose to be deprecated to begin with than lets restore it.
@vandonr-amz please also remove the manual note about this removal from the change log of 8.0.0 as if we restore then users don't need to take action

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:providers provider:amazon AWS/Amazon - related issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants