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

Azure functions should support versions other than [~1 beta] #1731

Closed
restfulhead opened this issue Aug 7, 2018 · 3 comments
Closed

Azure functions should support versions other than [~1 beta] #1731

restfulhead opened this issue Aug 7, 2018 · 3 comments

Comments

@restfulhead
Copy link

restfulhead commented Aug 7, 2018

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

Terraform v0.11.7

  • provider.azurerm v1.12.0

Affected Resource(s)

  • azurerm_function_app

Expected Behavior

I should be able to enter a specific version such as 2.0.11933-alpha. Currently I have to do this manually in the Azure portal. We currently can't use beta, because that version is broken for NodeJS deployments at the moment.

Actual Behavior

The following error is shown: expected version to be one of [~1 beta], got 2.0.11933-alpha.

I suggest to either remove the validation or adjust it so that you can specify values other than ~1 and beta.

What's frustrating about this bug is that when I change the version on Azure and I run terraform apply whith beta as the version, TF wants to revert:

  ~ azurerm_function_app.my-functions-app
      version:                                   "~2" => "beta"

So I have to manually go in and change it back again each time I deploy changes. Is there a workaround to disable validations until it is fixed?

@JimPaine
Copy link
Contributor

JimPaine commented Sep 5, 2018

I hit the same issue when trying to pin my app for this breaking change

I have submitted a pull request to remove the validation allowing for furture versions and pinning of versions to work.

After looking through the Azure REST API I could see the validation was specific to this terraform provider.

Pull Request

@tombuildsstuff
Copy link
Contributor

Closing this since this has been fixed via #1872 which shipped as a part of v1.14

@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 👉 [email protected]. 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

No branches or pull requests

4 participants