PS>Get-PureOneCertificate -Export -ExportDirectory "c:\temp"
Please enter a certificate export password: ****
ConvertFrom-SecureString : A parameter cannot be found that matches parameter name 'AsPlainText'.

This is due to no support on PowerShell 5.1 for -asplaintext. Adding alternative code path if PowerShell 5 is in use

Add an import parameter to New-PureOneCertificate so pfx files can be imported into the certificate store appropriately.

On the Pure PowerShell code, when pulling the files, we are getting the columns combined in the file.

I have to manually separate out the columns.

Is it possible to update the powershell code to make this happen automatically ?

Here is the example.

Get-PureOneVolume

This cmdlet call shows the first two columns fine. But third column is a combination of four columns. We have to manually separate them.

Get-PureOneVolume | Select id, name , @{Expression={$.arrays.id -join ';' }} , @{Expression={$.arrays.name -join ';' }} , `

@{Expression={$.arrays.resource_type -join ';' }} , @{Expression={$.arrays.fqdn -join ';' }} , created, destroyed , eradicated , pod , provisioned , serial , source , _as_of

Same goes for other cmdlets
Get-PureOneFileSystem
Get-PureOneArrayTag

Please let me know if you can do it internally on the above mentioned cmdlets.

With the 1.4.x.x release there is a new default cert/key feature. The cmdlets should be enhanced to not require a cert or private key if the default is desired. Cmdlets:

Get-PureOnePublicKey, New-PureOneJwt, New-PureOneConnection

For some reason, the get-pureonevolumesnapshot operation does not scale well with the default result limit of 1,000. Seems to tip over at a 1,000. So I implemented a new global variable $global:PureOneRateLimit that controls how many responses are returned per REST operation for requests that use the continuation token (volumes, snapshots). The snapshot one will default to 500 unless you override by setting that variable to something else. Volumes will continue to default to whatever the default is, currently 1,000. If you set the variable though it will use that number too.

Will follow up with Pure1 as to why this is happening. If it hits the error though it will pause for 5 seconds and retry.

Add support to the PureOneOrganization class to support having a private key and password instead of a Windows certificate.

If you pass in multiple certificates in the new-pureonejwt (and some other) cmdlet it will sign the JWT with ALL of the certs creating an invalid JWT.

Need to add error handling and improved cert creation to help with this.

When support for Unix was added it broke pipelining support for Windows certificates. So the following:

$cert | New-PureOneJwt -PureAppID myAPPid

Asks you for the Unix private key. This is likely due to pipeline objects being processed last and causing PowerShell to select the wrong parameter set. Not sure how to fix this yet. For now the workaround is to pass in the certificate not via pipeline, so like:

New-PureOneJwt -PureAppID myAPPid -Certificate $cert

There is no support for continuation tokens, which means items returned max out at 1,000.

When a target metric passed to the Get-PureOneMetric command has a single availability defined (includes granularity and metrics history available time range), we can use the granularity and the available time range as defaults if no granularity and/or start time were specified via input the parameters of the command.
If there are multiple availabilities defined for a metric, those parameters (granularity and start time) need to be specified explicitly, since it's not clear which availability definition to use as defaults.

Following error after authentication and pulling arrays list:
`
New-PureOneConnection -certificate $certObject -pureAppID "blahblahblah"
$arrays = @()
$arrays = Get-PureOneArray
$arrays | select | where {$_.name -like "MYTESTARRAY"}

#-We get a values list of Arrays (id/hosts redacted):
id : xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
name : MYTESTARRAY
fqdn : MYTESTARRAY.FDQN
model : FA-X20R2
os : Purity//FA
version : 6.0.0
_as_of : 1599061801000

#-/api/1.latest/alerts
$alerts = New-PureOneOperation -resourceType "alerts" -queryFilter "?names='MYTESTARRAY'" -restOperationType GET

No access token found in the global variable or passed in. Run the cmdlet New-PureOneRestConnection to authenticate.
At C:\Program Files\WindowsPowerShell\Modules\purestorage.pure1\PureStorage.Pure1.psm1:2078 char:9

•     throw "No access token found in the global variable or passed ...
  

•     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : OperationStopped: (No access token...o authenticate.:String) [], RuntimeException
  • FullyQualifiedErrorId : No access token found in the global variable or passed in. Run the cmdlet New-PureOneRestConnection to authenticate.
    `

$Global:DefaultPureOneConnection does not appear to be set as manually setting it to the active $Global:PureOneConnections

Does appear to carry on, but does not retrieve resources.

Add ability to specify Pure1 org in cmdlets.

Make the cmdlets iterate through all organizations in the global variable. Or use what is passed in.

Add a cmdlet to remove Pure1 connections.

If only one existing session: remove it with no parameters.

If more than one connection: require org ID or access token.

Mandatory parameters not defined in certain cmdlets, so Pure1 throws error. Should be handled client side.

<location>Get-PureOnePublicKey Please enter your RSA private key password: *********** Exception: Public key could not be generated. Confirm password and/or permission access to private key

Issue retrieving the public key on Linux/Mac

Generate public key from RSA private key in Get-PureOnePublicKey for Linux or Mac users.

Currently PowerShell sessions expire after 10 hours, and the default JWT is good for 30 days. I will add semantics to catch expired sessions and refresh if the JWT is still good. If the JWT is expired that should be on the user to re-create the JWT.

No parameter sets defined, therefore a lot of unnecessary checks in the code.

For consistency, and code simplicity, move all custom invoke-restmethod operations to custom new-pureonerestoperation.

Properties can be manually updated, but that does nothing, so they should be read only and changes disallowed.

Currently there is no advanced debug logging. Adding write-debug where appropriate so when run with -debug more information can be gleaned

Ggracefully handle multiple connection retries on same Pure1 org. If 2nd+ connection for same org is attempted fail and ensure that it is not listed in $Global:PureOneConnections.

New-PureOneOperation throws non-terminating errors when the Pure1 REST service returns an error response which causes cascading errors. Setting ErrorActionPreference to stop temporarily and then reverting so it ends upon REST failure

New-SelfSignedCertificate: /home/pureuser/.local/share/powershell/Modules/PureStorage.Pure1/1.1.0.0/PureStorage.Pure1.psm1:47
Line |
47 | $CertObj = New-SelfSignedCertificate -certstorelocation $cert …
| ~~~~~~~~~~~~~~~~~~~~~~~~~
| The term 'New-SelfSignedCertificate' is not recognized as the name of a cmdlet, function, script file,
| or operable program. Check the spelling of the name, or if a path was included, verify that the path
| is correct and try again.

This is due to not being able to use certificates and needs to use OpenSSL instead. Will work on updating it.

Since RSA private key pairs use passwords, we can have the New-PureOneConnection detect the default key pair and if present (and of course if no specific one was passed in) automatically use that. This will allow users of the default created key pair (at /home//PureOnePrivate.pem to not have to pass the key location in upon each initial login and only require the password and the Pure1 app ID.

Creating a new Pure1 connection or generating a JWT throws an error:

Can't open ./PureOneSignedHeader.txt for reading, No such file or directory
140496100544960:error:02001002:system library:fopen:No such file or directory:../crypto/bio/bss_file.c:72:fopen('./PureOneSignedHeader.txt','rb')
140496100544960:error:2006D080:BIO routines:BIO_new_file:no such file:../crypto/bio/bss_file.c:79:

This does not cause the operation to fail, but it looks like it does. This is due to a race condition between commands for openssl.

Support for RSA Private key in PEM format for creating a new connection.

To make it easier to lookup a cert, there will be a designation of the default cert. This will be set automatically moving forward, but if you would like to change default certs or designate a manually created one this cmdlet will set the specified cert as default.

On get-pureonearray or get-pureonevolume (and others) add metric switch parameters to retrieve certain metrics. Thinking like -space or -performance

New cmdlet to retrieve subscriptions and licenses.

Pass in openssl-created PEM file for private key. Encrypted or not to New-PureOneJWT

If you create a certificate and immediately try to create a JWT (after putting the public key in Pure1) it fails with an error of cannot find private key in PowerShell core only. There seems to be some lag with the creation of the private key and it does not appear in the powershell object storing the cert. The fix is to refresh the cert in the new-pureonecertificate cmdlet so it is fully created:

 $CertObj = Get-ChildItem -Path $CertObj.PSPath
  return $CertObj

Will add this in next release.

Export the in-use certificate for migration or backup

When there is no specific query but needs a continuation token, the query becomes malformed and gets stuck in a loop. A new check needs to be added to stop this.

Build an internal function to assemble query strings for REST calls, this will reduce complexity of all cmdlets and make it easier to troubleshoot and add features.

Code to check for token is re-used a lot, let's replace it with an internal function to simplify/reduce code.

Instead of looking for REST token in each one, create one function to check for passed in token or if not present, global token and then convert it into the proper header style and return it.

I should re-use the code in the cmdlet new-pureonerestoperation so that the code gets continually tested and so as Pure1 adds REST features it is easier to add support.

get-pureonevolume -volumename returns all volumes instead of just a single one

If you enter an invalid key or api key, the cmdlet throws errors but does not terminate on the first one, causing a bunch of needless errors

This returns the current support contracts for discovered arrays in Pure1. Start date and end date.

Incorrect logic detecting Windows when running PowerShell 5.x.

This will allow a script or user to use a JWT only to authenticate with Pure1, without needing a cert, key pair, or app ID

Throw an error if cannot connect with pointer towards the following requirements:
https://support.purestorage.com/Pure1/Pure1_Manage/013_Pure1_Manage_-_REST_API/Pure1_Manage_-_REST_API__Reference#Firewall_Access

Create a new cmdlet that can retrieve previously created certificates easily.

The help sections of the cmdlets are not fully written, these need to be populated to help with ease of use.

Create custom object called PureOneOrganization

Stores session information and has a method to renew the session.

get-help Get-PureOneArrayLoadMeter -Examples
-------------------------- EXAMPLE 4 --------------------------
PS > PS C:\ Get-PureOneArrayBusyMeter -objectName flasharray-m50-1 -startTime (get-date).AddDays(-1) -startTime (get-date).AddDays(-1) -granularity 86400000 -maximum (edited)

Add audit commands

Add cmdlet to pull alerts from Pure1