changing the trivy container API to just trivy so that users can reta…

…in regular functionality as before since trivy was the API argument for container images previously. At the UI level it will still display Trivy Container Image

backend/lambdas/api/repo/repo/util/const.py

@@ -25,7 +25,7 @@
         "owasp_dependency_check": None,
         "php_sensio_security_checker": None,
         "bundler_audit": None,
-        "trivy_image": None,
+        "trivy": None,
         "trivy_sca": None,
     },
     "secret": {"gitsecrets": None, "truffle_hog": None},
@@ -94,7 +94,7 @@
     # Add the Aqua plugin if it is enabled
     PLUGIN_LIST_BY_CATEGORY["vulnerability"]["aqua_cli_scanner"] = None
     for i in QUALIFIED_PLUGINS["vulnerability"]:
-        if i == ["trivy_image" or "trivy_sca"]:
+        if i == ["trivy" or "trivy_sca"]:
             # Set aqua_cli_scanner as an alternate option to trivy for qualification
             i.append("aqua_cli_scanner")
 else:

ui/src/app/scanPlugins.ts

@@ -179,8 +179,8 @@ export const vulnPluginsKeys: ScanPluginKeys = {
 	},
 	snyk: { displayName: t`Snyk`, apiName: "snyk", group: GROUP_VULN },
 	trivy_image: {
-		displayName: t`Trivy Container Images`,
-		apiName: "trivy_image",
+		displayName: t`Trivy Container Image`,
+		apiName: "trivy",
 		group: GROUP_VULN,
 	},
 	trivy_sca: {