In my setup, I have a set of discovered elements, and for each one, I would like to configure a couple of parameters during the provisioning.
In the help, when editing a CI type, it is possible to configure a script for the update of the properties, but I wonder if this the correct place to achieve what I need. It seemed to be even more natural to use the Configuration section, but I wonder if there is a straightforward way to do such initial configuration.
In my case, it’s necessary to configure the OIDs used by the protocol to communicate with the element, so I guess this only applies in such particular situations where additional setup is needed even to start talking with the element. This is why I think that such pre-step should be done during provisioning and not during the post configuration process.
There are two ways to perform actions after a Provisioning of Elements. As you are saying, you can configure a script to update properties (or any other actions that can only be done with an Automation Script).
The second way is to configure the 'Password Setup' in the Provisioning section of your CI Type. As the name says, it's initially meant to configure a password setup, but it can also be used to perform Parameters in a defined order.
You can configure the 'Password Setup' by going to the IDP Application, navigate to Admin > CI Types > Provsioning and click on the 'Advanced...' button for the CI Type you want. In the script that will open, you can click on 'Setup...'. You will get redirected to a screen where you can add Write parameters in a defined order. Save your CI Type and you're good to go!
Thanks. I finally used the password setup section and worked as expected. We should consider renaming this section to give it a broader scope of what can be possible to configure with it.
Indeed, it can cover an even broader set of use cases apparently.
Just to continue on your comments. The Password Setup was created upon request of Product Marketing and was only meant for configuring the credentials. We can revise this with Product Marketing, if that is still their point of view.
Great question. Just out of curiosity: would there be a reason to combine specific configurations on the discovered elements (the parameter sets you refer to) with the provisioning of the element into DataMiner? Because indeed, the configuration part of IDP is all about making sure that you have a proper base line configuration of onboarded elements, before you start using those for service provisioning. But that’s typically something done separately, after the provisioning into DataMiner. So just wondering if this is a specific use case (i.e. are those parameters somehow maybe linked with the provisioning into DataMiner, and do you need to make sure that happens every time as part of that process)?