COMMUNITY: Add support for Codacy in Argo CD based deploymet

[shailesh-vaidya]

Problem Statement

• Add support for Codacy in Argo CD based deploymet

Design

• For Bug, Describe the fix here.
• For Feature, Post the link for design

Coding

Checklist for Author

• [x] Coding conventions are followed and code is consistent

Testing

Checklist for Author

• [ ] Unit and System Tests are added
• [ ] Test Cases cover Happy Path, Non-Happy Path and Scalability
• [ ] Testing was performed with RPM
• [x] Jenkins pipelines used for testing - Validated in a staging environment https://cortx-re-vm-6805.pun.seagate.com:31450/applications?showFavorites=false&proj=&sync=&health=&namespace=&cluster=&labels=

Impact Analysis

Checklist for Author/Reviewer/GateKeeper

• [ ] Interface change (if any) are documented
• [ ] Side effects on other features (deployment/upgrade)
• [ ] Dependencies on other component(s)

Review Checklist

Checklist for Author

• [x] Jira ID/ COMMUNITY is prefixed in PR title Prefix Syntax - CORTX-<5 digit JIRA ID>: <PR Title> - for Seagate Employees COMMUNITY: <PR Title> - for open source contributors
• [x] PR is self reviewed
• [x] Jira and state/status is updated and JIRA is updated with PR link
• [x] Check if the description is clear and explained

Documentation

Checklist for Author

• [ ] Changes done to WIKI / Confluence page / Quick Start Guide

---

View rendered solutions/dashboard/ElasticsearchKibanaInstallation.md View rendered solutions/dashboard/README.md View rendered solutions/dashboard/deployment/README.md

[cla-bot[bot]]

Thanks for your contribution! The CLA bot has flagged your contribution as not having a Contributor License Agreement in place. Note that this is not needed in the overwhelming majority of instances and this warning will usually be ignored. The code reviewers will make a determination and may ask you to sign a CLA or may choose to ignore this warning. More information about this can be found here.