Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Terraform 1.6.x Fails due to plugin framework issue #506

Closed
1 task done
SeanKilleen opened this issue Oct 26, 2023 · 2 comments
Closed
1 task done

[BUG] Terraform 1.6.x Fails due to plugin framework issue #506

SeanKilleen opened this issue Oct 26, 2023 · 2 comments
Assignees
Labels
bug Something isn't working duplicate This issue or pull request already exists

Comments

@SeanKilleen
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

What version of Terraform are you using?

1.6.2

What type of issue are you facing

bug report

Describe the bug

After upgrading go Terraform v1.6.x, I receive errors along the lines of No data source type named "btp_directory" was found in the provider.

If the SAP BTP team is building the terraform plugin on the v1.4.x provider, you may need to update to the latest bugfix or roll back to 1.3.x in order to resolve this

Reference: hashicorp/terraform#33990

For now, I have to downgrade my Terraform to v1.5.x in order to work with the BTP providers it seems.

Expected Behavior

No response

Steps To Reproduce

No response

Add screenshots to help explain your problem

No response

Additional context

No response

@SeanKilleen SeanKilleen added bug Something isn't working needs-triage For new issues labels Oct 26, 2023
@lechnerc77 lechnerc77 removed the needs-triage For new issues label Oct 27, 2023
@lechnerc77 lechnerc77 self-assigned this Oct 27, 2023
@lechnerc77 lechnerc77 added the duplicate This issue or pull request already exists label Oct 27, 2023
@lechnerc77
Copy link
Member

Hi @SeanKilleen ,

yes this is a known limitation at the moment. The fix is already implemented and will be shipped with the next release.

For details and workarounds see #477.

@SeanKilleen
Copy link
Contributor Author

Thanks, and sorry for the duplicate! I checked the issues but missed it somehow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants