issue with base config on self hosted renovate #30831
-
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 problemI 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 {"$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)
Logs (2)
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 3 replies
-
Does your |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
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:
Thanks, the Renovate team |
Beta Was this translation helpful? Give feedback.
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.