You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a super minor issue, and I stumbled across this by accident.
When running a cmdlet with the -verbose switch, messages are being returned back without the function name in the "Load API Data for " statement
See the line in bold below.
I have found this to be true with all cmdlets in the module.
The reason for this is that in Get-RubrikAPIData, each cmdlet definition is missing the "Function" Key and value.
Depending on when this gets looked at, Get-RubrikDatabase, may have been fixed as a my last update to the module corrected this issue for that cmdlet. However, other cmdlets will have the same issue.
Provide information about the failure by issuing the command using the -Verbose command.
get-rubrikdatabase -name stackoverflow -verbose
VERBOSE: Validate the Rubrik token exists
VERBOSE: Found a Rubrik token for authentication
VERBOSE: Gather API Data for Get-RubrikDatabase
VERBOSE: Selected 1.0 API Data for Get-RubrikDatabase
**VERBOSE: Load API data for**
VERBOSE: Description: Returns a list of summary information for Microsoft SQL databases.
VERBOSE: Build the URI
VERBOSE: URI = https://amer1-rbk01.rubrikdemo.com/api/v1/mssql/db
VERBOSE: Build the query parameters for instance_id,primary_cluster_id,effective_sla_domain_id
VERBOSE: Query = Found limit flag
VERBOSE: URI = https://amer1-rbk01.rubrikdemo.com/api/v1/mssql/db?limit=9999
VERBOSE: Submitting the request
VERBOSE: GET https://amer1-rbk01.rubrikdemo.com/api/v1/mssql/db?limit=9999 with 0-byte payload
VERBOSE: received 1667508-byte response of content type application/json; charset=UTF-8
VERBOSE: Received HTTP Status 200
VERBOSE: Formatting return value
VERBOSE: Filter the results
VERBOSE: Filter match = Instance
VERBOSE: Filter match = Name
VERBOSE: Filter match = Hostname
VERBOSE: Filter match = SLA
Expected Behavior:
See line in bold below
get-rubrikdatabase -name stackoverflow -verbose
VERBOSE: Validate the Rubrik token exists
VERBOSE: Found a Rubrik token for authentication
VERBOSE: Gather API Data for Get-RubrikDatabase
VERBOSE: Selected 1.0 API Data for Get-RubrikDatabase
**VERBOSE: Load API data for Get-RubrikDatabase**
VERBOSE: Description: Returns a list of summary information for Microsoft SQL databases.
VERBOSE: Build the URI
VERBOSE: URI = https://amer1-rbk01.rubrikdemo.com/api/v1/mssql/db
VERBOSE: Build the query parameters for instance_id,primary_cluster_id,effective_sla_domain_id
VERBOSE: Query = Found limit flag
VERBOSE: URI = https://amer1-rbk01.rubrikdemo.com/api/v1/mssql/db?limit=9999
VERBOSE: Submitting the request
VERBOSE: GET https://amer1-rbk01.rubrikdemo.com/api/v1/mssql/db?limit=9999 with 0-byte payload
VERBOSE: received 1667508-byte response of content type application/json; charset=UTF-8
VERBOSE: Received HTTP Status 200
VERBOSE: Formatting return value
VERBOSE: Filter the results
VERBOSE: Filter match = Instance
VERBOSE: Filter match = Name
VERBOSE: Filter match = Hostname
VERBOSE: Filter match = SLA
Steps to Reproduce:
Please provide detailed steps for reproducing the issue.
run any cmdlet with -verbose. Regardless of parameters provided.
The text was updated successfully, but these errors were encountered:
This is a super minor issue, and I stumbled across this by accident.
When running a cmdlet with the -verbose switch, messages are being returned back without the function name in the "Load API Data for " statement
See the line in bold below.
I have found this to be true with all cmdlets in the module.
The reason for this is that in Get-RubrikAPIData, each cmdlet definition is missing the "Function" Key and value.
Depending on when this gets looked at, Get-RubrikDatabase, may have been fixed as a my last update to the module corrected this issue for that cmdlet. However, other cmdlets will have the same issue.
Provide information about the failure by issuing the command using the
-Verbose
command.Expected Behavior:
See line in bold below
Steps to Reproduce:
Please provide detailed steps for reproducing the issue.
run any cmdlet with -verbose. Regardless of parameters provided.
The text was updated successfully, but these errors were encountered: