1.2.3

Feature

• Stop using the NoValidation parameter. It is better to avoid unwanted behavior. (#10)

Update

• Invoke-PasmBlueprint
• Invoke-PasmAutomation
• README.md

1.2.2

Feature

• Fix the sample template so that the quota limit is not exceeded. (#8)

Update

• Invoke-PasmInitialize
• README.md

1.2.1

Feature

• Implemented id validation to initialization process using regular expressions. (#6)

Update

• Invoke-PasmInitialize

Caution

• This is only a validation using regular expressions and does not guarantee that the ID actually exists.

1.2.0

Feature

• Implemented aliases. (#4)

Update

• Invoke-PasmInitialize
• Invoke-PasmValidation
• Invoke-PasmBlueprint
• Invoke-PasmDeployment
• Invoke-PasmAutomation

Usage

psmi -p 'C:\' -n 'Pasm' -vpc 'your-vpc-id' -sbn 'your-subnet-id-1', 'your-subnet-id-2'
psmv -file 'C:\Pasm\outline.yml'
psmb -file 'C:\Pasm\outline.yml' -out 'blueprint.yml' -nv
psmd -file 'C:\Pasm\blueprint.yml'
psma -file 'C:\Pasm\outline.yml' -out 'blueprint.yml'

1.1.0

Feature

• The VpcId and SubnetId of the sample template created in the initialization process can now be overwritten.

Update

• Invoke-PasmInitialize

Usage

$param = @{
    VpcId    = 'vpc-1qaz2wsx3edc4rfv5'
    SubnetId = 'subnet-zxcvasdfqwer12345', 'subnet-poiulkjhmnbv09876'
}
Invoke-PasmInitialize @param

Caution

• If you overwrite the VpcId or AssociationSubnetId, be sure to run Invoke-PasmValidation to validate the template.

1.0.0

First release