As a global enterprise with strict security practices, we cannot send or store clear text passwords to the API. Please create a PowerShell Module that makes use of the secure string variable type or allow your API to accept this variable type and do the conversion on the server instead of the client.
If you were to create the PowerShell module, you would provide us with the ability to pull in information from many of our systems to populate custom fields. for example we have a web system that tracks application owner and because the xml pages end in a predictive fashion we can run it through the exported .csv file from device 42 and update thousands of records. but currently we have to download the custom field XML then convert the file to .csv then run our PowerShell script to update the .csv then save it back to a xml and re-upload it. this is just one of the scenarios we use to input data into Device42.
Most of your customers are likely to be operating in data centers that are predominantly hosting Microsoft operating systems. Adding a PowerShell integration will allow for easier acceptance and adoption of your application for these people as they can use it to promote their own automation efforts in the data center.
Any update on this request?3
+1 from us2
+1 from us too.1
We ended up creating a local user in Device42 with limited read access, wrote a saved DOQL query, and then just accessed it with Invoke-WebRequest. If you access the DOQL query URL with Invoke-WebRequest:
And save the results to a variable, then you can just use Convert-FromCsv to get it into a manageable set of objects.
Still clunky, but easy enough to get data out at least.0
Please sign in to leave a comment.