-
Hi, I maintain a few providers for my employer and we are investing how to support OpenTofu in our development process. One main issue we come across is executing acceptance tests using OpenTofu CLI. I set the env var
Is there extra steps I need to do or code to change in order to test against OpenTofu CLI? Would there be a migration doc/guide for provider developers like for regular users? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Hey @alexhung this is really useful, thank you. I opened an issue from this discussion as it seems to be a bug. We were debating if the legacy namespace thing was still in use or if it's something long gone. This should work out of the box and we'll look into why it's broken. /cc @Yantrio @cube2222 To answer your question about the provider development flow, ideally it should be the same process, but if it's more than just pointing |
Beta Was this translation helpful? Give feedback.
-
Hi @alexhung thank you for raising this. I've tracked this down to a choice of hardcoding some parameters in the plugin testing code here To work around this, when testing with tofu you can set the following environment variables:
I have successfully cloned and run the Please try this out and let us know how you get on! I'm happy to help with any other snags you hit whilst doing acceptance testing of providers with OpenTofu. |
Beta Was this translation helpful? Give feedback.
Hi @alexhung thank you for raising this.
I've tracked this down to a choice of hardcoding some parameters in the plugin testing code here
To work around this, when testing with tofu you can set the following environment variables:
I have successfully cloned and run the
TestAccRemoteUpgradeFromVersionWithNoDisableProxyAttr
test from your provider repository using these environment variables.Please try this out and let us know how you get on! I'm happy to help with any other snags you hit whilst doing acceptance testing of providers with OpenTofu.