-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PSRemotely maintain each node configuration #16
Labels
Comments
Also adding the ability to connect to a specific PSRemoting endpoint (JEA endpoint #4 ) would fall in place with this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: