Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / stelligent/test-platform issues and pull requests
#21 - Use CfnStacknamePrefixParameter in Parameter Store instead of hard coding in Python
Issue -
State: open - Opened by PaulDuvall about 7 years ago
#20 - Use CloudWatch Dashboards instead of S3 to host Dashboard
Issue -
State: open - Opened by PaulDuvall about 7 years ago
#19 - Add cloudformation_templates to Test Platform
Issue -
State: open - Opened by tleavey about 7 years ago
#18 - Add inspector-status to Test Platform
Issue -
State: open - Opened by tleavey about 7 years ago
#17 - Add config-rule-status to Test Platform
Issue -
State: open - Opened by tleavey about 7 years ago
#16 - Add cfn-nag to Test Platform
Issue -
State: open - Opened by tleavey about 7 years ago
#15 - Add mu to Test Platform
Issue -
State: open - Opened by tleavey about 7 years ago
#14 - Incorporate aws-devsecops-workshop into the automated tests
Issue -
State: open - Opened by PaulDuvall about 7 years ago
#13 - Get notified when test-platform CFN stack error occurs
Issue -
State: open - Opened by PaulDuvall about 7 years ago
- 1 comment
#12 - Create a StelligentTest badge that indicates success/failure
Issue -
State: open - Opened by PaulDuvall about 7 years ago
#11 - Remove all hardcoded values from buildspec
Issue -
State: open - Opened by PaulDuvall about 7 years ago
#10 - Scan GitHub repositories in an organization to look for configuration files
Issue -
State: open - Opened by PaulDuvall about 7 years ago
#9 - Create a standard configuration file for projects to follow
Issue -
State: open - Opened by PaulDuvall about 7 years ago
#8 - Automatically determine name of CodePipeline to execute
Issue -
State: open - Opened by PaulDuvall about 7 years ago
- 1 comment
#7 - Move initial stage in CP pipeline from CodeCommit to GitHub
Issue -
State: open - Opened by tleavey about 7 years ago
#6 - Make the list of results prettier/easier to read through.
Issue -
State: open - Opened by tleavey about 7 years ago
#5 - Automate the deletion of resources after stacks are created and the status checker runs.
Issue -
State: closed - Opened by tleavey about 7 years ago
- 1 comment
#4 - Concatenate/add the acronym of the status checker to the cfn stack names automatically. (Implement through buildspec)
Issue -
State: closed - Opened by tleavey about 7 years ago
- 1 comment
#3 - If one stack fails, the other stacks don't run/get checked.
Issue -
State: closed - Opened by tleavey about 7 years ago
- 1 comment
#2 - Depending on the status of a repo, add red/yellow/green icons in GitHub.
Issue -
State: open - Opened by tleavey about 7 years ago
#1 - We need the status checker results to be pushed into GitHub.
Issue -
State: closed - Opened by tleavey about 7 years ago
- 1 comment