Why is sticky_settings omitted from azurerm_{windows/linux}_web_app_slot and azurerm_{windows/linux}_function_app_slot?

We have a situation where we need sticky settings on the slot because we need to set the functions hostid to have unique values. There is a sticky_settings block for the main resource, but not the slot resource.

1 Like

Have the same issue, it’s frustrating…

All you have to do is set it on the “Web App” or “Function App” resource (the production slot). This is because ALL slots must either be “sticky” or not (think about it, how could it work otherwise). The rule is “Last In”… So if you set the Sticky Bit on any slot or Un-Set it on ANY slot, it will immediately update all the other slots. Make sense? I can find the documentation if needed…