Creating a v1 provider and v2 provider side-by-sid...
# azure
f
Creating a v1 provider and v2 provider side-by-side seems to be almost working. It wants to tear down and re-build the resource, since the provider changed - and I can't alias them to each other, as that throws a conflicting / duplicate resource error. I'm going to manually edit the statefiles such that it believes the provider hasn't changed; and we'll see what happens 🙂