AsBuiltReport / AsBuiltReport.Fortinet.FortiGate

Repository for AsBuiltReport Fortinet FortiGate module
MIT License
36 stars 9 forks source link

forticare: don't check BranchUpdateVersion #64

Closed alagoutte closed 5 months ago

alagoutte commented 5 months ago

there is already a check before

Fix #63

connorhess commented 5 months ago

I may have done something wrong with updating my files, but getting this error now

WARNING: The names of some imported commands from the module 'PowerFGT' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again
with the Verbose parameter. For a list of approved verbs, type Get-Verb.

Name                           Value
----                           -----
server                         **Redacted**
version                        7.4.1
invokeParams                   {UseBasicParsing, DisableKeepAlive, TimeoutSec}
headers                        {X-CSRFTOKEN}
port                           **Redacted**
httpOnly                       False
session                        Microsoft.PowerShell.Commands.WebRequestSession
serial                         **Redacted**
vdom

[ERROR] - New-AsBuiltReport : Cannot validate argument on parameter 'Report'. Invalid report type specified. Please use one of the following []
At C:\AsBuilt\running_command.ps1:10 char:27
+ New-AsBuiltReport -Report Fortinet.FortiGate -Target $Server -Usernam ...
+                           ~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (:) [New-AsBuiltReport], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationError,New-AsBuiltReport

if it is updating that caused this, please advise how i can update the packages, (at scale) we have multiple PC's running the script.

alagoutte commented 5 months ago

You need to import-module with -force after change file

(you don't need to use connect-fgt before also...)

You need to wait a new release (for next week/month i think...)