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

provider: Migrate to standalone plugin SDK v1.1.1 #4474

Merged
merged 3 commits into from
Oct 7, 2019

Conversation

radeksimko
Copy link
Member

@radeksimko radeksimko commented Oct 1, 2019

Depends on hashicorp/terraform-provider-azuread#154


I didn't run any acceptance tests for this one (yet).

@radeksimko radeksimko requested a review from a team October 1, 2019 13:59
@ghost ghost added the size/XXL label Oct 1, 2019
@tombuildsstuff tombuildsstuff added this to the v1.36.0 milestone Oct 1, 2019
@radeksimko
Copy link
Member Author

I'm not sure what's going on with Travis - I was not able to reproduce the build failures myself locally nor in clean Docker golang:1.13.1

@tombuildsstuff
Copy link
Contributor

@radeksimko now that hashicorp/terraform-provider-azuread#154's been merged would you mind rebasing this?

@radeksimko radeksimko changed the title provider: Migrate to standalone plugin SDK v1.1.0 provider: Migrate to standalone plugin SDK v1.1.1 Oct 7, 2019
@radeksimko
Copy link
Member Author

@tombuildsstuff rebased, PTAL

Copy link
Contributor

@tombuildsstuff tombuildsstuff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@tombuildsstuff tombuildsstuff merged commit 107b131 into master Oct 7, 2019
@tombuildsstuff tombuildsstuff deleted the sdk-migration branch October 7, 2019 06:41
tombuildsstuff added a commit that referenced this pull request Oct 7, 2019
abhinavdahiya added a commit to abhinavdahiya/installer that referenced this pull request Oct 8, 2019
…ndle private_dns zone

Using the upstream azurerm provider is not possible for now because of following reasons:

1) There is not srv record resource for private dns zone

2) The version of provider that has the private dns zone resources `1.34.0` has a lot of bugs like
    * hashicorp/terraform-provider-azurerm#4452
    * hashicorp/terraform-provider-azurerm#4453
    * hashicorp/terraform-provider-azurerm#4501
    Some of these bugs are fixed, and some are in flight.

    Another reason moving to `1.36.0` which might have all the fixes we need is the provider has moved to using
    `standalone terraform plugin SDK v1.1.1` [1]. Because we vendor both terraform and providers, this causes errors like
    `panic: gob: registering duplicate types for "github.com/zclconf/go-cty/cty.primitiveType": cty.primitiveType != cty.primitiveType`

   Therefore, we would have to move towards a single vendor for terraform and plugins for correct inter-operation, which is tricker due to conflicts elsewhere

A simple 4 resource plugin that re-uses the already vendored azurerm provider as library and carries over the required resources seems like an easy fix for now.

[1]: hashicorp/terraform-provider-azurerm#4474
@ghost
Copy link

ghost commented Oct 29, 2019

This has been released in version 1.36.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 1.36.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Nov 6, 2019

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Nov 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants