Add AWS S3 bucket support

[Sarafian]

With the assumption that the AWSPowerShell module is installed.

With AWS S3 support we could download https://s3-eu-west-1.amazonaws.com/cloudformation-templates-eu-west-1/Windows_Single_Server_SharePoint_Foundation.template with something like this

something = @{
        DependencyType = 'AWS-S3'
        BucketName = 'cloudformation-templates'
        Region = 'eu-west-1' #Optional
        Key='Windows_Single_Server_SharePoint_Foundation.template'
    }

We need to consider authentication but as a first version we could it is setup on your profile with Set-AWSCredentials

[RamblingCookieMonster]

Cool idea! Any interest at taking a stab at this? Haven't used much AWS yet : )

Cheers!

[Sarafian]

Since I've created this issue I've already taken a look into the code. I understand where the actually dependency type implementation needs to be created but can you provide some insight for the rest of the source code? A couple of questions

• Is it just enough to add an entry in the PSDependMap.psd1?
• I've seen messages about certain parameters not being supported by a DependencyType. Where does the push of the configured parameters happen to the DependencyType script?
• Do you have a preference on how to make sure the AWSPowerShell module is installed/available?

I'm already working on something similar here. Once I finish this and I know a bit more I'll do the contribution.

[Sarafian]

Notes for the future. The cmdlet that will support this dependency is Copy-S3Object. Required parameters are:

• the bucket name
• the key
• target path. Can be file or folder path for our requirements.

All cmdlets in AWSPowerShell module define many optional parameters that drive the authorization. Optional parameters are:

• Region
• ProfileName
• ProfilePath
• SessionToken
• AccessKey
• SecretKey

Skipped the ones with credentials as they shouldn't be added to the configuration script. To decouple sensitive information from the configuration script, we need to define expressions that when invoked returned the intended object. For example for a property Credential we need a CredentialExpression that has the ability to return the intended value.

[RamblingCookieMonster]

Hi!

Gotcha:

• Yep! Just add an entry to PSDependMap.psd1, and drop the script you point to in PSDependScripts.
• I think in some of my examples I used PSDependOptions (global) with parameters specific to dependencytypes. We detect valid parameters here, and either add or warn user-provided parameters here. I only throw warnings to give a little flexibility - we don't have 'globalish-parameters-for-a-particular-dependencytype,' so occasionally folks might throw in a parameter in PSDependOptions that applies to most but not all of there dependencies.
• No preference on how you handle AWSPowerShell, apart from keeping the logic in the dependency script. Some options you could use:
  • You could specify a default spot to look in the PSDepend.config - this is parsed and sets module level variables in the psm1 - you could then use that variable in your dependency script - assuming there's only one spot to look - tough if you want to allow flexibility (e.g. might be in any psmodulepath)
  • You could use any method to pull it down, but, do keep in mind that we bootstrap nuget.exe and place it in the module root - you could rely on the NugetPath module variable for this - benefit is that it will work on systems without PowerShellGet. Caveat is that PSDepend running on a locked down system where a user has not configured an alternate nugetpath, or installed nuget in their path, won't pull things down - presumably they couldn't pull down the AWS module at that point, so maybe a moot point.

Cheers!

[Sarafian]

Pull request available #30