File matched by custom fileMatch but not taken as package file

[YinleXu]

What would you like help with?

I would like help with my configuration

How are you running Renovate?

Self-hosted

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

Gitlab, renovate version 37.408.0

Please tell us more about your question or problem

I have an ansible galaxy dependency file with name "requirements_galaxy.yml". This does not match the default pattern

"(^|/)(galaxy|requirements)(\\.ansible)?\\.ya?ml$"

Therefore I have added fileMatch config in the repo's renovate.json config file

"ansible-galaxy":{
    "fileMatch": ["(^|/)requirements_galaxy.ya?ml$"],
    "enabled": true
}

With this config, I can see the file being matched from the debug log but it seems it is not being treated as a package file. Therefore, no MR/PR was created for the dependencies in the file. See more details in the logs.

I have recreated the same issue with this Github repo. You can see the galaxy.ansible.yml file, which is matched by the default pattern, gets PRs created while requirements_galaxy.yml with same content did not. Although the file was actually matched evidently from the debug log.

Am I missing any config in addition to "fileMatch"?

Logs (if relevant)

Logs

DEBUG: Matched 2 file(s) for manager ansible-galaxy: galaxy.ansible.yml, requirements_galaxy.yml (repository=YinleXu/renovate_test)
DEBUG: Matched 1 file(s) for manager pip_requirements: requirements.txt (repository=YinleXu/renovate_test)
DEBUG: manager extract durations (ms) (repository=YinleXu/renovate_test)
       "managers": {"pip_requirements": 2, "ansible-galaxy": 2}
DEBUG: Found ansible-galaxy package files (repository=YinleXu/renovate_test)
DEBUG: Found pip_requirements package files (repository=YinleXu/renovate_test)
DEBUG: Found 2 package file(s) (repository=YinleXu/renovate_test)
 INFO: Dependency extraction complete (repository=YinleXu/renovate_test, baseBranch=main)
       "stats": {
         "managers": {
           "ansible-galaxy": {"fileCount": 1, "depCount": 4},
           "pip_requirements": {"fileCount": 1, "depCount": 2}
         },
         "total": {"fileCount": 2, "depCount": 6}

[rarkins]

Most likely the file you're matching does not contain the same file structure which renovate is expecting for ansible galaxy

[YinleXu]

hi @rarkins , thanks for replying. However, the two files have exactly the same content, one being copy of the other. However, galaxy.ansible.yml (default matching) got PRs created while requirements_galaxy.yml did not.

[rarkins]

It seems that the ansible-galaxy manager has a check for file name patterns within it too:

renovate/lib/modules/manager/ansible-galaxy/extract.ts

Lines 30 to 38 in 1c3dbca

	const galaxyFileNameRegEx = regEx(/galaxy\.ya?ml$/);
	const deps: PackageDependency[] = [];
	const lines = content.split(newlineRegex);
	try {
	// if this is a galaxy.yml file we have to interpret the dependencies differently
	if (galaxyFileNameRegEx.exec(packageFile)) {
	const galaxyDeps = extractCollectionsMetaDataFile(lines);
	deps.push(...galaxyDeps);

@secustor could this be replaced with a check on content instead of file name?

[secustor]

With the support for schemas while parsing YAML that should be possible now.

[rarkins]

Converted to issue: #29816