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

Support for function_app vnet integration #6267

Closed
buissjer opened this issue Mar 26, 2020 · 2 comments
Closed

Support for function_app vnet integration #6267

buissjer opened this issue Mar 26, 2020 · 2 comments
Labels

Comments

@buissjer
Copy link

buissjer commented Mar 26, 2020

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

Description

The field virtual_network_name was removed from the site_config block since azurerm provider version 2.0.
I'm currently working in a previous version which allow me to use this field in an ignore_changes block like following (for both app_service and app_function):

  lifecycle {
    ignore_changes = [
      site_config[0].vnetName,
      app_settings
    ]

I need this to avoid breaking the vnet integration did by ARM templates.

How can I do the same in 2.0 version?

New or Affected Resource(s)

  • azurerm_app_service
  • azurerm_function_app
@favoretti
Copy link
Collaborator

Since this issue has been reported a long time ago and relates to the version of provider we no longer support - I'm going to close it. Please open a new updated bug report on current versions of terraform and provider if this is still relevant. Thank you.

@github-actions
Copy link

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 21, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants