-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feat/ssm parameters unit test example #274
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## develop #274 +/- ##
===========================================
- Coverage 96.42% 95.99% -0.43%
===========================================
Files 10 10
Lines 643 674 +31
Branches 134 143 +9
===========================================
+ Hits 620 647 +27
- Misses 14 16 +2
- Partials 9 11 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Hi @shadycuz, is there any chance you'd be able to merge a few of the open PRs? Thanks. |
Adds to the
examples/unit
directory a readme file and two sample test cases showing covering testing parameters are valid.This includes the additional functionality to support SSM parameter types, which close #270 and complete #202. This also adds the ability to load parameters from configuration files (supporting the CodePipeline artifact and CloudFormation CLI configuration file options).
I've added in
isort
as a pre-commit hook and changed flake8 to use this for checking import order too to save needing to manually reorder imports. It is pretty much the same check that was there before. When I was recreating myvenv
it was failing to install so I've set the minimum taskcat version to the latest, hope that is ok.@shadycuz I suggest that this feature triggers a new release and we explore the naming/hook piece for the release after.