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
With the current implementation of PSRemotely, the required modules and required artefacts are assumed to be the same.
For Example - if a Manifest.xml is set to be one of the required artefacts then it gets copied to all the nodes.
Now this served our purpose well in a Remote ops validation of an Engineered solution but PSRemotely should have the ability to have Node specific or a group specific way of supplying these configurations.
This would get aligned well, when we start using classes.
The text was updated successfully, but these errors were encountered:
With the current implementation of PSRemotely, the required modules and required artefacts are assumed to be the same.
For Example - if a Manifest.xml is set to be one of the required artefacts then it gets copied to all the nodes.
Now this served our purpose well in a Remote ops validation of an Engineered solution but PSRemotely should have the ability to have Node specific or a group specific way of supplying these configurations.
This would get aligned well, when we start using classes.
The text was updated successfully, but these errors were encountered: