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

Deprecate azurerm_app_service_plan properties block for top level fields #2442

Merged
merged 5 commits into from
Dec 4, 2018

Conversation

katbyte
Copy link
Collaborator

@katbyte katbyte commented Dec 4, 2018

No description provided.

@katbyte katbyte added this to the 1.20.0 milestone Dec 4, 2018
@ghost ghost added the size/L label Dec 4, 2018
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.

one minor thing to fix but this otherwise LGTM 👍

}

d.Set("maximum_number_of_workers", props.MaximumNumberOfWorkers)
Copy link
Contributor

Choose a reason for hiding this comment

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

since this is a *int32 we need to cast this to an int here

@katbyte katbyte merged commit f566b36 into master Dec 4, 2018
@katbyte katbyte deleted the app-service/properties branch December 4, 2018 18:10
katbyte added a commit that referenced this pull request Dec 4, 2018
@ghost
Copy link

ghost commented Mar 5, 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 👉 hashibot-feedback@hashicorp.com. Thanks!

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

Successfully merging this pull request may close these issues.

2 participants