Copy the application log settings when cloning deployment slots
It would be better if the log settings are copied into a newly created slot, when we clone a slot, just like the app settings does.
For example, currently when we turn the blob logging enabled and then clone the slot, the logging get disabled in a new slot.
On the contrary, the blob container settings remains.
This is because the blob container setting is saved as an environment variable in app settings.
Here is the result in ResourceExplorer, when I cloned a slot.
"sasUrl": "<a rel="nofollow noreferrer" href="https://strageaccountsample.table.core.windows.net/xxxxxxx"">https://strageaccountsample.table.core.windows.net/xxxxxxx"</a>;
This is a great feature request for our deployment slots. We’ll leave this idea open for now to see if it gains more support so we can prioritize the work on our roadmap.