Catesta is a PowerShell module and vault project generator. It uses templates to rapidly scaffold test and build integration for a variety of CI/CD platforms.
Home Page: https://www.catesta.dev/
License: MIT License
I'm a Senior Systems Development Engineer at AWS. I write code and use modern technology practices to create highly robust, secure, and performant enterprise solutions.
Module name should be replaced during deployment for SampleInfraTest.Tests.ps1
Module name is not replaced.
Remains as: # $ModuleName = '<%=$PLASTER_PARAM_ModuleName%>
Line 194 specifying codepipeline should have a !Sub Intrinsic function to specify the region
Currently the !Sub is missing and causes the CFN to fail validation.
Add !Sub Intrinsic function
If you test the individually and then build the module you aren't accurately testing the code that you're shipping, simple things like $script: or $global: variables may be set in functions that break interactions in other functions but pass the tests. There are also other more complex interactions that can occur with the dot sourcing process (assuming the individual function tests are importing the psd1 or psm1 rather than just the individual function file) which don't occur when all the functions are in a single file.
Have the test and analyze steps depend on the build step. It takes a tiny amount of time to combine the ps1 files into a psm1 so it's well worth doing it first.
As a side benefit this will also speed up tests which import the module with -Force since dot sourcing is really slow. It'll not be noticeable for small modules but for bigger ones or ones with lots of tests that many imports will have an impact on test time.
When AWS CI/CD choice is used and S3 bucket is provided install_modules.ps1 should have S3 bucket name replaced.
BucketName = '<%=$PLASTER_PARAM_S3Bucket%>'
It only leaves the variable:
BucketName = $PLASTER_PARAM_S3Bucket
Octopus Deploy is a Ci CD Tool that has its origins firmly in the land of PowerShell and still keeps it firmly in mind to this day. Whilst they did remove the free for evaluation version for a while, that options now back and it would be good if Catesta could support it.
https://octopus.com/
Evaluate level of effort to add Pester 5 support to Catesta module scaffolding.
Give users the ability to scaffold module projects that will be engaging Pester 5+
Likely want to keep Pester 4 support for the time being so give users a choice if possible.
Manifest info in build header does not display correct information
Manifest Info should display useful manifest information.
Manifest Info: System.Collections.HashtableAdjust manifest information to display manifest version.
When running invoke-build the Set-BuildHeader separates tasks and provides a clean output with useful information.
Currently, one of those is only putting out a hashtable (Manifest Info).
This should be corrected to display relevant information about the manifest during the build.
When as S3 bucket is provided for AWS install_modules the $temppath should be set for them to be downloaded.
The $tempPath variable is not set. This causes the download to fail.
$tempPath = [System.IO.Path]::GetTempPath()
GitHub actions supports a matrix construct for jobs. This may be more efficient than having entirely separate workflows setup for multiple OS module testing.
Test and evaluate if matrix is a better fit for cross-platform module testing than separate GA workflows per platform.
New V2 version of task publishing code coverage results is available to all our customers now. We highly recommend to stop using the V1 version and migrate to V2 version (https://learn.microsoft.com/azure/devops/pipelines/tasks/reference/publish-code-coverage-results-v2). For more details, see - https://devblogs.microsoft.com/devops/new-pccr-task.
Currently set to PublishCodeCoverageResults@1. Update to v2.
After module build is completed the BuildTask should cleanup leftover artifacts.
Once module build is complete the Imports.ps1 is left behind despite having been merged into the psm1.
Add a step in the cleanup process to remove the Imports.ps1 file.
When doing module only it should state that a module only is deployed.
New-PowerShellProject -CICDChoice 'ModuleOnly' -DestinationPath .
Scaffolding your PowerShell Module for GitHub Actions...
@dganev-cb filed PR #58 highlight an issue with the Paths regarding the case of the folder Editor
Catesta should operate as expected on all supported OS's.
Incorrect casing seems to be causing an issue on a Linux based OS when running Catesta.
Correct casing related to Editor.
Potentially explore other casing issues as well.
See screenshot in #58
Unknown. @dganev-cb can you prove your environment details?
$PSVersionTable.OS:$PSVersionTable.PSEdition:Explore casing issues that may be causing an issue with Catesta on Linux based operating systems. Test on a variety of Linux based hosts and correct the Editor casing as well as explore other potential casing issues.
During build process CreateMarkdownHelp step should be able to successfully create markdown and external help from inline help.
Checking for missing documentation in md files...
The documentation that got generated resulted in missing sections which should be filled out.
Please review the following sections in your comment based help, fill out missing information and rerun this build:
(Note: This can happen if the .EXTERNALHELP CBH is defined for a function before running this build.)
Path of files with issues: D:\Code\Git\path\moduleName\src\Artifacts\docs\
Filename LineNumber Line
-------- ---------- ----
Get-Function1.md 189 {{Fill ProgressAction Description}}
Get-Function2.md 143 {{Fill ProgressAction Description}}
Get-Function3.md 146 {{Fill ProgressAction Description}}
ERROR: Missing documentation. Please review and rebuild.
At D:\Code\Git\path\moduleName\src\moduleName.build.ps1:405 char:9
+ throw 'Missing documentation. Please review and rebuild.'
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
At D:\Code\Git\path\moduleName\src\moduleName.build.ps1:349 char:1
+ Add-BuildTask CreateMarkdownHelp -After CreateHelpStart {Generated Markdown file contains the following:
### -ProgressAction
{{Fill ProgressAction Description}}This looks to be related to a breaking change introduced in PowerShell 7.4.0.:
Added the ProgressAction parameter to the Common Parameters
$PSVersionTable.OS: Microsoft Windows 10.0.22000$PSVersionTable.PSEdition: CoreName Value
---- -----
PSVersion 7.4.1
PSEdition Core
GitCommitId 7.4.1
OS Microsoft Windows 10.0.22000
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0Unable to run builds that support help creation at this time.
An overhauled version of platyPS is now available. Evaluate this new version and determine if it resolves some of the help creation issues previosly faced allowing for an upgrade off version 0.12.0
Evaluate new capabilities of platyPS redesign and see if it meets the needs for Catesta help generation.
Catesta has been locked to version 0.12.0 because of a text replacement issue during build:
PowerShell/platyPS#457
As mentioned in #33 - Catesta does not always correctly identify missing example using count.
This can be improved by switching to a null check on the example content.
Adjust all ExportedFunctions.Tests.ps1 references to switch from count to content check
tasks.json should be valid json
^ currently missing comma in tasks json
add comma
Add support for BitBucket to Catesta
Catesta can scaffold modules that are stored in BitBucket repos and support BitBucket pipelines
As part of getting started with Catesta, I had to dig through the code base to find where to import the module dependencies for my PowerShell module. I found the actions_bootstrap.ps1 file, and determined that I needed to add my module imports there.
For additional context, I was not able to initially start using Catesta until I added my module imports to the actions_bootstrap.ps1 script, as my tests were failing due to missing module dependencies.
I noticed a note in the build.ps1 script about dependency installation not being included, but was not able to find further documentation on that comment.
See this failed action for an example of the error I ran into, and this commit for how I resolved this issue.
Ideally, during setup, Catesta would have an additional prompt that asks you which modules you would like to install as dependencies. This should add the required modules to the module manifest and the appropriate workflow script.
Alternatively, update/add documentation on how to avoid this issue for users getting started with Catesta.
Example broken action run: https://github.com/TsekNet/TsekProfile/runs/1078982174?check_suite_focus=true
Fixed issue in my repo: TsekNet/TsekProfile@2257337
PowerShell 5.1 is not honoring the Filter for merging files into the psm1 in some scenarios during the build phase. When files that share a ps1 extension like a .ps1xml are being included
.ps1xml files should not be merged into the final module during build phase.
When a ps1xml file is placed in the root of the build currently (common practice) PowerShell 5.1 includes it in the .ps1 filter and adds it to the final psm1 file.
$powerShellScripts = Get-ChildItem -Path $script:ArtifactsPath -Filter '*.ps1' -Recurse
# to
$powerShellScripts = Get-ChildItem -Path $script:ArtifactsPath -Recurse | Where-Object {$_.Name -match '^*.ps1$'}This does not occur in higher versions of PowerShell
New project scaffold should work
/local/home/user/workspaces/moduleName/src/moduleName> New-PowerShellProject -CICDChoice 'ModuleOnly' -DestinationPath .
Scaffolding your PowerShell Module for GitHub Actions...
Create docs/
Create media/
Create src/
Create src\Archive/
Create src\Artifacts/
Create src\Tests/
Create src\Tests\Infrastructure/
Create src\Tests\Unit/
Create src\moduleName/
Create src\moduleName\Public/
Create src\moduleName\Private/
Create src/Tests/Unit/moduleName-Module.Tests.ps1
Create src/Tests/Unit/ExportedFunctions.Tests.ps1
Create src/Tests/Unit/moduleName-Function.Tests.ps1
New-PowerShellProject: Cannot find path '/home/user/.local/share/powershell/Modules/Catesta/0.10.2/Resources/Vanilla/../Module/src/Tests/Infrastructure/SampleInfraTest.Tests.ps1' because it does not exist.
Success
-------
False
ModuleType Version PreRelease Name PSEdition ExportedCommands
---------- ------- ---------- ---- --------- ----------------
Script 0.10.2 Catesta Desk {New-PowerShellProject, New-VaultProjec…
Catesta does not support a namespaced module name (ex. MyModule.Utils)
Simply support module names with a dot/period.
At a glance, it seems a simple change to Module.build.ps1 $ModuleName parsing will address this.
From
$ModuleName = (Split-Path -Path $BuildFile -Leaf).Split('.')[0]
and $script:ModuleName = (Split-Path -Path $BuildFile -Leaf).Split('.')[0]
To
$ModuleName = ((Get-Item $BuildFile).BaseName) -replace ".build$"
and $script:ModuleName = ((Get-Item $BuildFile).BaseName) -replace ".build$"
The vanilla module and vanilla vault never prompt the user if they want to replace comment based help with auto-generated external help
<parameter name='Help' type='choice' default='0' store='text' prompt='Would you like to use platyPS to generate help documentation files for your project?'>
<choice label='&Yes' help="platyPS will generate MarkDown help and external xml help" value="Yes"/>
<choice label='&No' help="No help files will be generated." value="No"/>
</parameter>
The CreateMarkdownHelp task fails (technically platyPS fails) when trying to generate Markdown help if the module being tested is not already installed locally.
I'll leave it up to you whether this is a critical issue or not, but this was a blocker for me getting started using Catesta. Not importing the module as to not interfere with local modules may be WAI, but I did not see this in the FAQ/documentation. PowerShell module scopes may help resolve this.
platyPS generates the markdown docs without issue. This requires (at least in its current implementation) that the module is first installed.
The module build fails with the error below:
Task /./CreateHelpStart/CreateMarkdownHelp : Build markdown help files for module and fail if help information is missing
At D:\projects\testmodule\testmodule\src\test.build.ps1:276
Manifest File: D:\projects\testmodule\testmodule\src\test\test.psd1
Manifest Version: 0.1.0
Generating markdown files...
ERROR: Module test is not imported in the session. Run 'Import-Module test'.
At C:\Program Files\WindowsPowerShell\Modules\platyPS\0.12.0\platyPS.psm1:261 char:25
+ ... throw "Module $_ is not imported in the session. Run 'Imp ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
At D:\projects\testmodule\testmodule\src\test.build.ps1:276 char:1
+ Add-BuildTask CreateMarkdownHelp -After CreateHelpStart {
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
At D:\projects\testmodule\testmodule\src\test.build.ps1:267 char:1
+ Add-BuildTask CreateHelpStart {
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
At D:\projects\testmodule\testmodule\src\test.build.ps1:41 char:1
+ Add-BuildTask -Name . -Jobs $str
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Build FAILED. 8 tasks, 1 errors, 0 warnings 00:00:03.0509986
Module test is not imported in the session. Run 'Import-Module test'.
At C:\Program Files\WindowsPowerShell\Modules\platyPS\0.12.0\platyPS.psm1:261 char:25
+ ... throw "Module $_ is not imported in the session. Run 'Imp ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: (Module test is ...t-Module test'.:String) [], RuntimeException
+ FullyQualifiedErrorId : Module test is not imported in the session. Run 'Import-Module test'.Add the following to the CreateHelpStart task, you'll likely want to use -Force here as to reinstall the module that was just built.
Write-Build Gray " Importing $ModuleName v$ModuleVersion ..."
Import-Module -Name $script:ModuleManifestFile -Global -Force -PassThru -ErrorAction Stop
Write-Build Gray " ...$ModuleName imported successfully."You may also want to add removing this module at the beginning of every run's cleanup.
Invoke-Build from the src directory$PSVersionTable.OS:$PSVersionTable.PSEdition:OS: win10-2004 ($PSVersionTable.OS does not exist on PowerShell 5.1)
$PSVersionTable
Name Value
---- -----
PSVersion 5.1.19041.1
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.19041.1
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1Buildspec file should download, install, and run PS7
Incorrectly references PS6 path:
- powershell -command '.\configure_aws_credential.ps1'
- aws s3 cp s3://bucket/PowerShell-7.0.0-win-x64.msi PowerShell-7.0.0-win-x64.msi --quiet
- powershell -command "Start-Process $env:CODEBUILD_SRC_DIR\PowerShell-7.0.0-win-x64.msi -ArgumentList '/qn /norestart' -Wait" - '& "C:\Program Files\PowerShell\6\pwsh.exe" -command ''.\install_modules.ps1'''
Change to reference PS7 path
Specified modules should download to the temp directory of the build container when an S3 bucket is specified as a source.
When S3 bucket is specified as source build container fails to download modules.
$tempPath is currently incorrectly commented out in install_modules.ps1
GitHub now supports adding a SECURITY.md file to a repo for giving people instructions for reporting security vulnerabilities in a project.
Catesta could include a template example of this file for scaffolding GitHub based projects.
Add a SECURITY.md file for GitHub project templates: Adding a security policy to your repository
N/A
N/A
Extending the scaffolding to offer some additional convenience features in the build would be nice.
Any additional features would presumably exist as additional items in the module generation schema and thus would be presented as opt-in choices during module generation.
FunctionsToExport during the build process, would be useful.I guess the obvious alternative is to inject your own build and pipeline files after generation, or to fork the project to customize things in the first place. Personally I'd rather minimize making my own private changes when I feel that they are probably changes that many others can benefit from -- I feel it undermines the spirit of sharing and open source a little.
Kudos on a cool project! Appreciate the efforts you've put into it.
This is more of a nit FR, but it would be performant to leverage the platyPS Update-MarkdownHelp function over the New-MarkdownHelp function when generating documentation.
Update-MarkdownHelp doc: https://github.com/PowerShell/platyPS/blob/master/docs/Update-MarkdownHelp.md
New-MarkdownHelp doc: https://github.com/PowerShell/platyPS/blob/master/docs/New-MarkdownHelp.md
If the doc already exists for a given function, leverage Update-MarkdownHelp function over the New-MarkdownHelp function. This can be done with a PowerShell foreach loop and nested conditional.
New-Markdownhelp technically works, but it seems unnecessary to generate entirely new documentation files every time this module is built, especially if the function(s) have not been updated.
See platyPS module documentation here: https://github.com/PowerShell/platyPS
While generating docs, it looks like Catesta only writes documentation generated by platyPS to the artifacts folder. I'm not sure if this is WAI, but it would be useful to generate docs in the root directory (I'll leave the actual location up to you). Having docs in the root directory would make them more discoverable when someone is browsing a git repo, as they're immediately visible. Currently, docs are not automatically written to any directory that's uploaded to GitHub.
When the CreateMarkdownHelp task executes, docs are written to the root directory (alongside src, media, .vscode, etc.). Whether they also need to live in the artifacts dir, I'll leave up to you.
A scripted copy of the docs generated and written to the artifacts directory would be possible, to avoid unnecessary calls to platyPS and ensure the docs are always the same between the two directories.
I've manually copied the docs for now, but I'd like to hear your thoughts on how to address this.
As mentioned in #25 the throw message doesn't provided all the needed context of the error. A simple throw does.
Change actions_bootstrap.ps1 in all referenced locations from throw $message to throw
Assert-MockCalled is being deprecated in Pester 5:
THIS COMMAND IS OBSOLETE AND WILL BE REMOVED SOMEWHERE DURING v5 LIFETIME, USE Should -Invoke INSTEAD.
Remove use of Assert-MockCalled in all Pester 5 use cases throughout Catesta code base
Catesta already exports module members via the module manifest, there is no need to add Export-ModuleMember to the module as well. By default, creating a new module will fail due to the PSScriptAnalyzer rule that does not allow for wildcard exports in the module manifest, so this field must be modified for all modules to build successfully.
Catesta executes Export-ModuleMember -Function $public.Basename as part of every time the module is imported (link).
Remove Export-ModuleMember from the module itself, and leave this to the manifest. I will submit a PR for this.
$PSVersionTable.OS:$PSVersionTable.PSEdition:I'll note that this is not a high priority issue, this technically works, just the effort is duplicated. For context, this suggestion was taken from this Reddit post.
All Pester tests should use the new syntax with dashes
Cannot retrieve the dynamic parameters for the cmdlet. Legacy Should syntax (without dashes) is not supported in Pester 5. Please refer to migration guide at: https://pester.dev/docs/migrations/v3-to-v4
Dashes are not used in several of the pester tests scaffolds
All Pester tests, regardless of Pester 4 or 5 should use the new syntax
AWS CodeBuild now supports managed GitHub Action runners
Add Catesta workflow support for module projects that use CodeBuild and want to target GitHub Action runners
Dump of actions/choices leading to error:
❯ New-PowerShellProject -CICDChoice 'GitHubActions' -DestinationPath .\AvroTools
____ _ _
| _ \| | __ _ ___| |_ ___ _ __
| |_) | |/ _` / __| __/ _ \ '__|
| __/| | (_| \__ \ || __/ |
|_| |_|\__,_|___/\__\___|_|
v1.1.3
==================================================
Enter the name of the module: Avro
Enter a description for the module: Import Avro format files in PowerShell.
Enter the version number of the module (0.0.1): 1.0.0
Enter your full name (Oisin Grehan):
Would you like to generate a Changelog file?
[C] Changelog [N] None [?] Help (default is "C"):
Would you like to generate helpful repository files? (issue/pullrequest/feature)
[G] GitHub [N] None [?] Help (default is "G"):
Select a License for your module. (Help deciding: https://choosealicense.com/)
[M] MIT [A] Apache [G] GNU [I] ISC [N] None [?] Help (default is "M"): a
Would you like to generate a Code of Conduct file?
[C] conduct [N] None [?] Help (default is "C"): n
Would you like to generate a Contributing guidelines file?
[C] Contribute [N] None [?] Help (default is "C"): n
Would you like to specify a coding style for the project?
[S] Stroustrup [O] OTBS [A] Allman [N] None [?] Help (default is "S"):
Would you like to use platyPS to generate help documentation files for your project?
[Y] Yes [N] No [?] Help (default is "Y"): n
Select desired workflow action options? (If your module is cross-platform you should select multiple)
[W] Windows - PowerShell
[C] Core (Windows)- pwsh
[L] Linux
[M] MacOS
[?] Help
(default is "W")
Choice[0]: C
Choice[1]:
Scaffolding your PowerShell Module for GitHub Actions...
Create docs\
Create media\
Create src\
Create src\Archive\
Create src\Artifacts\
Create src\Tests\
Create src\Tests\Infrastructure\
Create src\Tests\Unit\
Create src\Avro\
Create src\Avro\Public\
Create src\Avro\Private\
Create .vscode\tasks.json
Create .vscode\extensions.json
Create .vscode\settings.json
Create src\Tests\Unit\Avro-Module.Tests.ps1
Create src\Tests\Unit\ExportedFunctions.Tests.ps1
Create src\Tests\Unit\Avro-Function.Tests.ps1
Create src\Tests\Infrastructure\SampleInfraTest.Tests.ps1
Create src\Avro\Public\Get-HelloWorld.ps1
Create src\Avro\Private\Get-PrivateHelloWorld.ps1
Create src\Avro.build.ps1
Create src\Avro.Settings.ps1
Create src\PSScriptAnalyzerSettings.psd1
Create actions_bootstrap.ps1
Create .gitignore
New-PowerShellProject: Cannot find path 'C:\Users\OisinGrehan\Documents\PowerShell\Modules\Catesta\0.10.0\Resources\GitHubActions\..\GitHubFiles\.gitignore' because it does not exist.
Presently, only the Vanilla module template prompts the user for a VSCode files choice:
<parameter name='VSCode' type='choice' default='0' store='text' prompt='Would you like to add helpful VSCode files for your project?'>
<choice label='&Yes' help="VSCode files will be added to make editing in VSCode easier." value="Yes"/>
<choice label='&No' help="VSCode files will not be added." value="No"/>
</parameter>
The rest of the templates just add the files natively.
Given the following:
I'm opting to just remove the singular prompt on the vanilla module template.
The default behavior moving forward will be that the VSCode files will be included during module creation.
The alternative would be to prompt the user to decide for VSCode files each time.
When the Build task is run, it should not fail if the docs folder has not been created.
Build task fails if the docs folder has not been created by the CreateHelp tasks workflow
Add if and Test-Path logic to check if the docs folder exists, and only perform a Move-Item if it does.
Clean and Build tasks without first running help generationName Value
---- -----
PSVersion 7.2.9
PSEdition Core
GitCommitId 7.2.9
OS Microsoft Windows 10.0.19045
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0When as S3 bucket is provided for AWS install_modules the $moduleInstallPath should be set for them to be installed to the correct location within the CodeBuild container.
The $moduleInstallPath is not set.
if ($PSVersionTable.Platform -eq 'Win32NT') {
$moduleInstallPath = [System.IO.Path]::Combine($env:ProgramFiles, 'WindowsPowerShell', 'Modules')
if ($PSEdition -eq 'Core') {
$moduleInstallPath = [System.IO.Path]::Combine($env:ProgramFiles, 'PowerShell', 'Modules')
}
else {
$moduleInstallPath = [System.IO.Path]::Combine($env:ProgramFiles, 'WindowsPowerShell', 'Modules')
}
}
elseif ($PSVersionTable.Platform -eq 'Unix') {
$moduleInstallPath = [System.IO.Path]::Combine('/', 'usr', 'local', 'share', 'powershell', 'Modules')
}
elseif ($PSEdition -eq 'Desktop') {
$moduleInstallPath = [System.IO.Path]::Combine($env:ProgramFiles, 'WindowsPowerShell', 'Modules')
}
else {
throw 'Unrecognized OS platform'
}
Pester 5 is out. Current templates scaffold with Pester 4.
Upgrade the dependencies and a few bits of test scripts to Pester 5?
Some of the other dependencies may also use an upgrade bump. (platyPS, InvokeBuild)
PlatyPS preview may fix the open issue.
https://github.com/PowerShell/platyPS/blob/v2/src/Model/Constants.cs
Having GitLab as one of the options for CICDChoice, would be helpful as it is also a widely used platform.
As mentioned in #25 - When Catesta detects missing comment-based help, it outputs the Matches property.
This can be improved by adding the LineNumber and Line propert to all build template references.
Adjust output of all *.build.ps1 references to include this change.
Infra tests should run post build.
Adjust InvokeBuild template to run infra tests after build is completed and reference the built module.
Discussed in #3
When creating a new AWS based project and an S3 bucket is specified for module download - the bucket name should be replaced in install_modules.ps1
Deployment of file still results in just the variable name:
BucketName = $PLASTER_PARAM_S3BucketCorrect the variable reference
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.