[🚨Error] multi repository configuration isn't supported. Only one repository configuration is allowed
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 107
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 5
Description
Describe the bug
According to this documentation one frogbot-config.yml can be used for multiple repositories:
https://docs.jfrog.com/security/docs/the-frogbot-config-yml-file-structure#can-one-frogbot-configyml-file-be-used-for-multiple-git-repositories
This isn't working for me. Does this require a certain version of xray to work? Here are my current versions:
14:40:16 [🔵Info] Frogbot version: 2.30.0
14:40:16 [Debug] Xray version: 3.111.23
14:40:16 [Debug] XSC version: 3.999.999
NOTE: This is working when only 1 repo is provided.
Current behavior
$ ./frogbot cfpr
14:40:16 [🔵Info] Frogbot version: 2.30.0
14:40:16 [Debug] Sending HTTP GET request to: https://artifactory.xxx.com/xray/api/v1/system/version
14:40:16 [Debug] Xray version: 3.111.23
14:40:16 [Debug] Sending HTTP GET request to: https://artifactory.xxx.com/xray/api/v1/xsc/system/version
14:40:16 [Debug] XSC version: 3.999.999
14:40:16 [Debug] Reading config from file system. Looking for .frogbot/frogbot-config.yml
14:40:16 [Debug] frogbot-config.yml wasn't found in /home/600001148/.frogbot/frogbot-config.yml. Searching for it in upstream directories
14:40:16 [Debug] Attempting to download frogbot-config.yml from DEVOPS/test-repo
14:40:16 [Debug] The frogbot-config.yml will be downloaded from develop branch
14:40:17 [🔵Info] Successfully downloaded frogbot-config.yml file from <DEVOPS/test-repo/develop>
14:40:17 [Debug] The content of frogbot-config.yml that will be used is:
- params:
Git parameters
git:
# [Mandatory]
# Name of the git repository to scan
repoName: DEVOPS/test-repo
[Mandatory]
# List of branches to scan
branches:
- develop
- master
- params:
Git parameters
git:
# [Mandatory]
# Name of the git repository to scan
repoName: DEVOPS/ansible
[Mandatory]
# List of branches to scan
branches:
- master
14:40:17 [Debug] Configuration Profile usage is disabled. All configurations will be derived from environment variables and files.
To enable a Configuration Profile, please set JF_USE_CONFIG_PROFILE to TRUE
14:40:17 [Debug] Sending HTTP HEAD request to: 'https://github.com/jfrog/frogbot'
14:40:17 [Debug] Locking config file to run config AddOrEdit command.
14:40:17 [Debug] Creating lock in: /tmp/jfrog.cli.temp.-1774377617-145806235/locks/config
14:40:17 [Debug] config file is released.
14:40:17 [Debug] Releasing lock: /tmp/jfrog.cli.temp.-1774377617-145806235/locks/config/jfrog-cli.conf.lck.4016670.1774377617785843216
14:40:17 [Debug] Artifactory Call Home: Sending info...
14:40:17 [🔵Info] Running Frogbot "scan-repository" command
14:40:17 [Debug] Sending HTTP POST request to: https://artifactory.xxx.com/artifactory/api/system/usage
14:40:17 [Debug] Sending HTTP GET request to: https://artifactory.xxx.com/xray/api/v1/system/version
14:40:18 [Debug] JFrog Xray version is: 3.111.23
14:40:18 [Debug] Sending HTTP POST request to: https://artifactory.xxx.com/xray/api/v1/usage/events/send
14:40:18 [Debug] Sending an error report to JFrog analytics...
14:40:18 [Debug] Sending HTTP POST request to: https://artifactory.xxx.com/xray/api/v1/xsc/event/logMessage
14:40:18 [🚨Error] multi repository configuration isn't supported. Only one repository configuration is allowed
Reproduction steps
No response
Expected behavior
No response
JFrog Frogbot version
2.30.0
Package manager info
None
Git provider
Bitbucket Server
JFrog Frogbot configuration yaml file
No response
Operating system type and version
Red Hat Enterprise Linux release 8.10 (Ootpa)
JFrog Xray version
3.111.23
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the frogbot cfpr command and the downloaded frogbot-config.yml shown in the report, comparing behavior with one repository versus multiple repository entries. The issue provides no reproduction steps or configuration file, so done means identifying why the documented multi-repository configuration is rejected and confirming the supported behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100