Hi
@flaky-arm-38472,
To be honest with you, I guess that is a common difference between providers that don’t need to be developed together. We can have a stable Azure Native provider and an AWS Native provider in a different state. You can check in public Pulumi Roadmap the progress of each component, provider, etc.:
https://github.com/orgs/pulumi/projects/44/views/4. Another source that I use frequently is the Release comparison to understand if a specific issue was gone:
https://github.com/pulumi/pulumi-aws-native/compare/v0.19.0...master. If we can have a proper release note, it will be better than this method, which is a bit complex, but it is what we have right now. In my personal TODO, I want to contribute to improving that area.
About the code, I can’t see the issue in using AWS Native and AWS Classic together because I’m using it, I guess most engineers are in the same boat. Standardising the IaC using only one will be better but is acceptable to have this transition.