You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unlike previous versions of FabricObserver (and ClusterObserver), the latest versions require that you create an instance of the service as a last step in your deployment script - IF you are not deploying via ARM. This is because ARM does not support the notion of Default services (and therefore DefaultServices configuration setting in ApplicationManifest.xml).
I have seen cases where folks are using older deployment scripts to push out the new release(s), but then only the Application(s) is created, not the service instance(s), which means nothing will happen. Services are the executables, not Applications.
Please remember to update your non-ARM deployment scripts to account for this change. In PowerShell, for example, you would complete deployment of FO 3.2.0.xxx like this:
This is documented on FO's main Readme and in the Release Notes, but I wanted to call this out in Discussions to make sure folks pay attention (assuming Discussions are read ;-)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Unlike previous versions of FabricObserver (and ClusterObserver), the latest versions require that you create an instance of the service as a last step in your deployment script - IF you are not deploying via ARM. This is because ARM does not support the notion of Default services (and therefore DefaultServices configuration setting in ApplicationManifest.xml).
I have seen cases where folks are using older deployment scripts to push out the new release(s), but then only the Application(s) is created, not the service instance(s), which means nothing will happen. Services are the executables, not Applications.
Please remember to update your non-ARM deployment scripts to account for this change. In PowerShell, for example, you would complete deployment of FO 3.2.0.xxx like this:
This is documented on FO's main Readme and in the Release Notes, but I wanted to call this out in Discussions to make sure folks pay attention (assuming Discussions are read ;-)
Hope this helps,
...Charles
Beta Was this translation helpful? Give feedback.
All reactions