issue with base config on self hosted renovate

[ReenigneArcher]

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.

github workflow with renovate via npm

Please tell us more about your question or problem

I cannot get renovate to use my base config in my repos.

I'm running renvoate via a GitHub workflow with the npm version of renovate.

I tried both of the following:

1:

      - name: Self-hosted Renovate
        env:
          LOG_LEVEL: debug
          RENOVATE_INHERIT_CONFIG: "true"
          RENOVATE_INHERIT_CONFIG_FILE_NAME: "renovate-config.json"
          RENOVATE_INHERIT_CONFIG_REPO_NAME: "${{ github.repository }}"
          RENOVATE_INHERIT_CONFIG_STRICT: "true"
          RENOVATE_REPOSITORIES: "my-org/ansible-repo"
          RENOVATE_REPOSITORY_CACHE: ${{ github.event.inputs.repoCache || 'enabled' }}  # use cache if this is set
          RENOVATE_TOKEN: ${{ secrets.RENOVATE_TOKEN }}
        run: |
          renovate

This runs but the resulting renovate.json config in the destination repo doesn't have my options and is just:

{"$schema": "https://docs.renovatebot.com/renovate-schema.json"}

The docs are not clear if the these env variables are for the self hosted config, or the repository config.

2:

      - name: Self-hosted Renovate
        env:
          LOG_LEVEL: debug
          RENOVATE_GLOBAL_EXTENDS: "github>${{ github.repository }}:renovate-config"
          RENOVATE_REPOSITORIES: "my-org/ansible-repo"
          RENOVATE_REPOSITORY_CACHE: ${{ github.event.inputs.repoCache || 'enabled' }}  # use cache if this is set
          RENOVATE_TOKEN: ${{ secrets.RENOVATE_TOKEN }}
        run: |
          renovate

I get a 404 error, relevant logs below.

I think the second option is the right approach, but these enterprise repos and not available without the token. How can I make sure my token is used with the GitHub API in this request?

As I investigate both logs, it seems like there might be a bug in renovate, as it appears both options hit the same GitHub API endpoint, but the first succeeds and the second doesn't.

Logs (if relevant)

Logs (1)

DEBUG: Checking for inherited config file renovate-config.json in repo my-org/renovatebot. (repository=my-org/ansible-repo)
DEBUG: http cache: saving https://api.github.com/repos/my-org/renovatebot/contents/renovate-config.json (etag=W/"redacted", lastModified=Fri, 16 Aug 2024 12:43:02 GMT) (repository=my-org/ansible-repo)
DEBUG: Inherited config (repository=my-org/ansible-repo)
       "config": {
         "$schema": "https://docs.renovatebot.com/renovate-schema.json",
         "description": ["Renovate onboarding preset"],
         "extends": ["github>my-org/renovatebot:renovate-config.json5"]
       }

Logs (2)

DEBUG: hostRules: no authentication for api.github.com
DEBUG: GET https://api.github.com/repos/my-org/renovatebot/contents/renovate-config.json = (code=ERR_NON_2XX_3XX_RESPONSE, statusCode=404 retryCount=0, duration=226)
DEBUG: Preset file renovate-config.json not found in my-org/renovatebot

[jamietanna]

Does your RENOVATE_TOKEN have contents: read for the my-org/renovatebot repository?

[ReenigneArcher]

Yes

[ReenigneArcher]

bump

[peter6667]

I assume you're trying to "copy renovate config" into a new repository, have you tried RENOVATE_ONBOARDING_CONFIG or RENOVATE_ONBOARDING_CONFIG_FILE_NAME?

RENOVATE_INHERIT_CONFIG should work on later invocations after "onboarding", so your current configuration should work, just not in the way you intended. That is, you get empty config in target repository (because you have not supplied any onboarding configuration) + the inherited one during execution, as explained in RENOVATE_INHERIT_CONFIG.

As far as authentication goes, I advise to read up on host rules. That's the extra configuration needed for access to protected repositories.

[ReenigneArcher]

Okay, thank you for the response. I did see RENOVATE_ONBOARDING_CONFIG but it didn't seem like what I wanted as I want this config for onboarding and after onboarding. Thanks for clarifying that the RENOVATE_INHERIT_CONFIG should work after onboarding.

This seemed to work though! The onboarding PR now has my preset config.

Now I have one more issue (I can open a separate discussion if that would be desirable).

This is my main config

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "description": [
    "Renovate onboarding preset"
  ],
  "extends": [
    "github>my-org/renovatebot:renovate-config.json5"
  ]
}

This is the config it extends

{
  // see https://docs.renovatebot.com/configuration-options
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "branchNameStrict": true,  // remove special characters from branch names
  "configMigration": false,  // allow renovate to open PRs to update config
  "constraintsFiltering": "strict",  // ensure dependencies are compatible with dependency constraints
  "description": "Renovate configuration for ansible",
  "extends": [
    "config:recommended",
    "group:recommended",
  ],
  "dependencyDashboard": false,  // Creates an issue with a "dashboard" of dependencies
  "dependencyDashboardLabels": [
    "dependencies"
  ],
  "labels": [
    "dependencies",
    "{{category}}"
  ],
  "prConcurrentLimit": 10,
  "rollbackPrs": true,  // create a rollback PR when a dependency is yanked
  "semanticCommits": "enabled",
  "updatePinnedDependencies": true,
  "packageRules": [
    {
      "enabled": false,
      "matchPackageNames": ["*"],
    },
    {
      "enabled": true,
      "matchManagers": ["ansible-galaxy"],  // only update ansible-galaxy dependencies
    },
  ],
}

Basically, I only want updates for Ansible dependencies in a requirements.yml file. But the onboarding PR has this content.

Welcome to [Renovate](https://github.com/renovatebot/renovate)! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.



---
### Detected Package Files

 * `requirements.yml` (ansible-galaxy)
 * `.github/workflows/ansible-lint.yml` (github-actions)
 * `.github/workflows/ansible-schedule.yml` (github-actions)
 * `.github/workflows/ansible-test.yml` (github-actions)
 * `.github/workflows/python-pytest.yml` (github-actions)
 * `.github/workflows/yaml-lint.yml` (github-actions)
 * `requirements-dev.txt` (pip_requirements)
 * `requirements.txt` (pip_requirements)

### Configuration Summary

Based on the default config's presets, Renovate will:

  - Start dependency updates only once this onboarding PR is merged
  - Renovate onboarding preset
  - Enable Renovate Dependency Dashboard creation.
  - Use semantic commit type `fix` for dependencies and `chore` for all others if semantic commits are in use.
  - Ignore `node_modules`, `bower_components`, `vendor` and various test/tests directories.
  - Group known monorepo packages together.
  - Use curated list of recommended non-monorepo package groupings.
  - Apply crowd-sourced package replacement rules.
  - Apply crowd-sourced workarounds for known problems with packages.
  - Use curated list of recommended non-monorepo package groupings.
  - Renovate configuration for ansible
  - Enable Renovate Dependency Dashboard creation.
  - Use semantic commit type `fix` for dependencies and `chore` for all others if semantic commits are in use.
  - Ignore `node_modules`, `bower_components`, `vendor` and various test/tests directories.
  - Group known monorepo packages together.
  - Use curated list of recommended non-monorepo package groupings.
  - Apply crowd-sourced package replacement rules.
  - Apply crowd-sourced workarounds for known problems with packages.
  - Use curated list of recommended non-monorepo package groupings.
  - Renovate configuration for ansible
  - Renovate onboarding preset

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to `renovate.json` in this branch. Renovate will update the Pull Request description the next time it runs.

---

### What to Expect

It looks like your repository dependencies are already up-to-date and no Pull Requests will be necessary right away.

---
> 
> [!WARNING]
> Please correct - or verify that you can safely ignore - these dependency lookup failures before you merge this PR.
> 
> -   `Can't find version matching 1.5.4 for galaxy-collection package ansible.posix`
> -   `Can't find version matching 9.2.0 for galaxy-collection package community.general`
> -   `Can't find version matching 3.0.0 for galaxy-collection package dellemc.powermax`
> -   `Can't find version matching 22.11.0 for galaxy-collection package netapp.ontap`
> 
> Files affected: `requirements.yml`


---

❓ Got questions? Check out Renovate's [Docs](https://docs.renovatebot.com/), particularly the Getting Started section.
If you need any further assistance then you can also [request help here](https://github.com/renovatebot/renovate/discussions).


---

This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).

<!--renovate-config-hash:0ce34766a2c42eab7905ce95d05d129d88e1cb53a9281a69098b9524e8062d6b-->

It detects the Ansible dependency file, but it also still detects other dependencies like python and github actions. And there is also a warning for every Ansible dependency. I'm able to install these dependencies in our runners so I wouldn't think it's a firewall issue. Any ideas?

[ReenigneArcher]

Now I have one more issue (I can open a separate discussion if that would be desirable).

Bot answer that, lol

[github-actions[bot]]

Hi there,

Please stick to one topic/question per Discussion. Start a new discussion per topic.

This prevents future users from finding this discussion and getting confused by multiple questions and answers. One question and answer per Discussion works best.

For example:

• Don't create a discussion with multiple questions requiring multiple answers
• If you got an answer to your first question, don't change topic like "Can I also ask you how I might..." which would then require a different answer. Mark the current discussion as answered and open a new one.

Thanks, the Renovate team