Azure-pipelines-tasks: Ambiguous (at best) explanation of setting 'Preserve VNet'

Created on 21 Sep 2018  路  10Comments  路  Source: microsoft/azure-pipelines-tasks

On the App Service Manage Swap Slots-task there is an extra setting called 'Preserve VNet'.
Swap slots task source

The 'help' text for this is "Preserve Virtual Network settings", which isn't really helpful in explaining what this setting actually does, it only explains the abbreviation 'VNet'.
Does this setting:

  1. Swap the Virtual Network also during the swap, as in it preserves the virtual network settings with the (contents of) source slot.
  2. Doesn't swap the Virtual Network during the swap, as in it preserves the virtual network settings on the target slot.

I couldn't find any helpful documentation on the microsoft-docs site either on this (same ambiguous explanation). Also note that English is not my native language.

Documentation Release

Most helpful comment

Why is this closed? I mean the checkbox tooltip is just as ambiguous as 2 years ago. A setting this important should be dumped down and very explicit to avoid mistakes

All 10 comments

This isn't descriptive either the -PreserveVnet parameter that probably is used under the hoot.

https://docs.microsoft.com/en-us/powershell/module/azurerm.websites/switch-azurermwebappslot?view=azurermps-6.13.0

Can you dispatch this question regarding missing documentation @bryanmacfarlane

Here is a bit more context on this. https://docs.microsoft.com/en-us/azure/app-service/deploy-staging-slots#which-settings-are-swapped

------------------snip---------------
When you clone configuration from another deployment slot, the cloned configuration is editable. Furthermore, some configuration elements follow the content across a swap (not slot specific) while other configuration elements stay in the same slot after a swap (slot specific).
------------------end snip-----------

Hope this helps

Hope this helps

@RoopeshNair No, it doesn't. According to https://docs.microsoft.com/en-us/azure/app-service/deploy-staging-slots#which-settings-are-swapped, the VNET Integration IS being swapped.

That being said, what does that _Preserve VNET_ checkbox do in addition to the VNET integration that is swapped along within a swap?

@RoopeshNair @kmkumaran ? please clarify.
I want to swap the VNET config I have added to my staging slot to the production slot during a swap.
Check it, or leave it unchecked in that case?

@markdebruijne - If you want to swap the vnet config, then leave it unchecked.
The task actually passes this preference (true or false) to Azure REST API.

image

Hi, I am trying to test and confirm this scenario and I found that if I have VNet integration (gateway required type) on my production slot and no VNet integration on my staging slot, then regardless of checking or unchecking "Preserve VNet", the production slot always has the VNet integration while my staging slot never has it. Is this expected? Are they only swapped if both slots have VNet integration configured?

Why is this closed? I mean the checkbox tooltip is just as ambiguous as 2 years ago. A setting this important should be dumped down and very explicit to avoid mistakes

@N-Usha - Can you review the feedback above and triage accordingly.

Why is this closed? Nothing has changed

Was this page helpful?
0 / 5 - 0 ratings