jsii
jsii copied to clipboard
aws
PowerShell Language Support
Hi CDK team, know. Know you support .NET but would love to see support extended to PowerShell Core.
@steven-cuthill-otm - sorry for the delay. We do have people working on a proof of concept that we are going to probably pursue more actively in the near future. Stay tuned!
Just for people tracking this issue, there was a very nice presentation done on the PowerShell Conference Europe regarding PowerShell support in the AWS CDK: https://www.youtube.com/watch?v=IjIHhZP_7RA.
@RomainMuller any update for us impatient souls on where that development stands?
Hi, is this worthy project still in the works? Any rough timeline? I've worked with CDK in Typescript but my tool of choice for everything AWS is Powershell and it would help take full advantage of CDK a lot faster. The PSCONF.EU video gave me hope but it's over a year old. I was hoping for a 2020 Re:invent announcement. I checked the CDK v1 and 2 roadmap and I do not see any trace of Powershell support. Please tell me PSCDK is still happening. Thank you for all your work.
I just watched that video, and commented on the video that they didn't share a link to the PSCDK project. Perhaps was abandoned?
Just my $.02 worth: it's pretty rare that AWS is behind Microsoft in tool availability. But with Bicep (which compiles to ARM JSON), they've made a big move to easing the burden on template development.
AWS should respond by making PowerShell interface with CDK so that it is easy for engineers (as opposed to developers) to create Cfn templates without having to learn CloudFormation YAML syntax.
Better yet: add a VS Code extension with IntelliSense to really accelerate the CDK adoption.
PowerShell, of course. :-)
One of the big issues, IMHO, with Cfn coding in VS Code is the lack of IntelliSense for either YAML or JSON in the AWS Toolkit extension for VS Code. It's a huge miss. You should see what the Bicep extension enables in VS Code. Cmd-spacebar is about 90% of coding an Azure template.
I know for C# that you get intellisense for referenced assemblies. For PowerShell, that's not the case? And that's the issue?
For those looking for a workaround, here is a sample repository showing one way to author CDK with PowerShell via the .NET assemblies for CDK: https://github.com/aws-samples/aws-cdk-powershell
