merge Develop to master (review in feature branch)

[dcchivian]

Description of PR purpose/changes

• Please include a summary of the change and which issue is fixed.
• Please also include relevant motivation and context.
• List any dependencies that are required for this change.

Jira Ticket / Issue

e.g. https://kbase-jira.atlassian.net/browse/DATAUP-X

• [ ] Added the Jira Ticket to the title of the PR e.g. (DATAUP-69 Adds a PR template)

Testing Instructions

• Details for how to test the PR:
• [ ] Tests pass in Travis-CI and locally

Dev Checklist:

• [ ] My code follows the guidelines at https://sites.google.com/truss.works/kbasetruss/development
• [ ] I have performed a self-review of my own code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation, including updating the README with app information changes
• [ ] My changes generate no new warnings
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] New and existing tests pass locally with my changes
• [ ] Any dependent changes have been merged and published in downstream modules

Updating Version and Release Notes (if applicable)

• [ ] Version has been bumped in kbase.yml
• [ ] Release notes have been updated for each release (and during the merge of feature branches)

[sonarcloud[bot]]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

No Coverage information
2.5% Duplication