-
Notifications
You must be signed in to change notification settings - Fork 87
Deprecate Frogbot env vars #973
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
Deprecate Frogbot env vars #973
Conversation
- Deleted .frogbot/frogbot-config.yml from repo root - Deleted testdata/config/ directory with all config test files - Deleted .frogbot directories from scanrepository test subdirectories - Removed configPath parameters from test functions - Removed config file validation from schema tests - Removed unused config file path constants - Cleaned up unused imports Config files are no longer used - all configuration now comes from environment variables only
# Conflicts: # .frogbot/frogbot-config.yml # scanrepository/scanmultiplerepositories_test.go # utils/params.go
- Delete schema/ directory (frogbot-schema.json, tests, testdata) - deprecated YAML config files - Delete docs/templates/jfrog-pipelines/ - deprecated JFrog Pipelines platform templates
- Delete TestExtractAndAssertRepoParams - tested config YAML param extraction - Delete TestBuildRepoAggregatorWithEmptyScan - tested empty scan in config YAML - Delete TestBuildMergedRepoAggregator - tested merging config YAML with env vars These tests are now redundant since config YAML functionality was removed. The functionality they tested (env var extraction, defaults) is covered by other existing tests.
The prepareConfigAndClient function was missing RepoName in gitTestParams, causing 'repository name is missing' error in tests after config YAML removal.
After config YAML removal, these tests lost their configurations: scanpullrequest tests: - ScanPullRequestNoFail: Set JF_FAIL=false - ScanPullRequestMultiWorkDir: Set JF_WORKING_DIR=sub1,sub3/sub4,sub2 + JF_REQUIREMENTS_FILE - ScanPullRequestMultiWorkDirNoFail: Same as above scanrepository tests: - aggregate-multi-dir: Set JF_WORKING_DIR=npm1,npm2 - aggregate-multi-project: Set JF_WORKING_DIR=npm,pip + JF_REQUIREMENTS_FILE These env vars replace the deleted config YAML files that previously provided these settings.
…PR_COMMENTS_DELETION, JF_AVOID_EXTRA_MESSAGES
- Update test to expect single combined branch 'frogbot-update-npm-Pip-dependencies-master' - Instead of separate branches for each technology - Aligns with new single-repository architecture that combines all technologies - Fixes test failure caused by removal of multi-repository support
- Update expected branch name from 'frogbot-update-npm-Pip-dependencies-master' - To 'frogbot-update-Pip-npm-dependencies-master' to match actual technology order - Technologies are processed in alphabetical order: Pip comes before npm
- Updated all field access to use repoConfig.Params.* pattern - Ensures consistency with scanrepository.go refactoring - Should fix vulnerability ordering in pull request tests
- Updated remaining field access patterns to use nested Params structure - Ensures full consistency across all scan commands
- Vulnerability order changed due to refactoring from config files to env vars - Python vulnerabilities now appear before npm vulnerabilities - This is the correct new behavior after removing multi-repo support
📗 Scan Summary
|
at 🎯 Static Application Security Testing (SAST) VulnerabilityFull descriptionVulnerability Details
OverviewStored Cross-Site Scripting (XSS) is a type of vulnerability where malicious Vulnerable examplefunc serveMessage(w http.ResponseWriter, r *http.Request) {
db, _ := sql.Open("sqlite3", "test.db")
message := db.QueryRow("SELECT message FROM messages WHERE id = 1")
fmt.Fprintf(w, "<h1>%s</h1>", message)
}In this example, the RemediationTo mitigate Stored XSS vulnerabilities, always sanitize and encode user func serveMessage(w http.ResponseWriter, r *http.Request) {
db, _ := sql.Open("sqlite3", "test.db")
message := db.QueryRow("SELECT message FROM messages WHERE id = 1")
- fmt.Fprintf(w, "<h1>%s</h1>", message)
+ fmt.Fprintf(w, "<h1>%s</h1>", html.EscapeString(message))
}In the remediation, we've used the Code FlowsVulnerable data flow analysis result
|
at 🎯 Static Application Security Testing (SAST) VulnerabilityFull descriptionVulnerability Details
OverviewStored Cross-Site Scripting (XSS) is a type of vulnerability where malicious Vulnerable examplefunc serveMessage(w http.ResponseWriter, r *http.Request) {
db, _ := sql.Open("sqlite3", "test.db")
message := db.QueryRow("SELECT message FROM messages WHERE id = 1")
fmt.Fprintf(w, "<h1>%s</h1>", message)
}In this example, the RemediationTo mitigate Stored XSS vulnerabilities, always sanitize and encode user func serveMessage(w http.ResponseWriter, r *http.Request) {
db, _ := sql.Open("sqlite3", "test.db")
message := db.QueryRow("SELECT message FROM messages WHERE id = 1")
- fmt.Fprintf(w, "<h1>%s</h1>", message)
+ fmt.Fprintf(w, "<h1>%s</h1>", html.EscapeString(message))
}In the remediation, we've used the Code FlowsVulnerable data flow analysis result
|
at 🎯 Static Application Security Testing (SAST) VulnerabilityFull descriptionVulnerability Details
OverviewStored Cross-Site Scripting (XSS) is a type of vulnerability where malicious Vulnerable examplefunc serveMessage(w http.ResponseWriter, r *http.Request) {
db, _ := sql.Open("sqlite3", "test.db")
message := db.QueryRow("SELECT message FROM messages WHERE id = 1")
fmt.Fprintf(w, "<h1>%s</h1>", message)
}In this example, the RemediationTo mitigate Stored XSS vulnerabilities, always sanitize and encode user func serveMessage(w http.ResponseWriter, r *http.Request) {
db, _ := sql.Open("sqlite3", "test.db")
message := db.QueryRow("SELECT message FROM messages WHERE id = 1")
- fmt.Fprintf(w, "<h1>%s</h1>", message)
+ fmt.Fprintf(w, "<h1>%s</h1>", html.EscapeString(message))
}In the remediation, we've used the Code FlowsVulnerable data flow analysis result
|
at 🎯 Static Application Security Testing (SAST) VulnerabilityFull descriptionVulnerability Details
OverviewStored Cross-Site Scripting (XSS) is a type of vulnerability where malicious Vulnerable examplefunc serveMessage(w http.ResponseWriter, r *http.Request) {
db, _ := sql.Open("sqlite3", "test.db")
message := db.QueryRow("SELECT message FROM messages WHERE id = 1")
fmt.Fprintf(w, "<h1>%s</h1>", message)
}In this example, the RemediationTo mitigate Stored XSS vulnerabilities, always sanitize and encode user func serveMessage(w http.ResponseWriter, r *http.Request) {
db, _ := sql.Open("sqlite3", "test.db")
message := db.QueryRow("SELECT message FROM messages WHERE id = 1")
- fmt.Fprintf(w, "<h1>%s</h1>", message)
+ fmt.Fprintf(w, "<h1>%s</h1>", html.EscapeString(message))
}In the remediation, we've used the Code FlowsVulnerable data flow analysis result
|


Uh oh!
There was an error while loading. Please reload this page.