When to use Associated Connector policy
-
-
ninaddate
Moderator2 years, 5 months ago #3490Do we need an instance of the Associated Connector policy defined and attached to a blueprinted entity only when a function for that entity is implemented in multiple languages or we need to always define this policy even if function code is implemented in one language?
-
This topic was modified 2 years, 5 months ago by
ninaddate.
-
This topic was modified 2 years, 5 months ago by
-
arumuganainar.s
Moderator2 years, 5 months ago #3493::This associated connector policy should be attached to the node if the function code body is implemented in any of the target languages such as bash, powershell, cisco commands etc., If the function is implemented in groovy, then there is no need to attach the connector policy. That is, if ignio needs to connect to the target machines to execute the function, then we need to attach the connector policy. The functions implemented in groovy are executed on the servers where ignio (core) is installed or on the proxy agent machine. So, for the the groovy functions, ignio does not use any connectors.
-
bana.sunit
Participant -
ninaddate
Moderator2 years, 5 months ago #3498::Thanks Nainar, Sunit for the explanation, that helps.
Sunit – only thing I did not understand is when you say in some cases connector policy comes by default and in some cases user has to define – can you help me understand which cases are you referring to, maybe some example will help [like do you mean older version of ignio it was available as default policy and newer versions it is not, or something else].-
bana.sunit
Participant
-
-
You must be logged in to reply to this topic.