Improve k8s manifest validation
Bug #1458879 reported by
hongbin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Magnum |
Fix Released
|
Undecided
|
Ronald Bradford | ||
Bug Description
When parsing k8s manifest, an exception should be raised if the inputted manifest is blank. Please see Tom's comment in the review below:
https:/
| tags: | added: tech-debt |
| Changed in magnum: | |
| assignee: | nobody → Ronald Bradford (ronaldbradford) |
| Changed in magnum: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to magnum (master) | #1 |
| Changed in magnum: | |
| status: | In Progress → Fix Committed |
| Changed in magnum: | |
| milestone: | none → mitaka-1 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit d3e041b785f9e4a
Author: Ronald Bradford <email address hidden>
Date: Mon May 25 17:19:28 2015 -0400
Improving Unit Test coverage of k8s_manifest
In addition these tests are used to provide a documented example
to demonstrate writing unit tests for new contributors for
increasing project code coverage.
Change-Id: I8448bf9ea05051
Closes-Bug: #1458879
Partially-