[JENKINS-75824] Export configuration as code for rest api key not supported

[jenkins-infra-bot]

We have to use Gerrit REST API due to Sonarqube requirements. We also use jenkins configuration as code for our jenkins config. However, we would like to keep the REST API key (protected, same as Jenkins secrets), so I would expect when exporting the config, the rest API key would be correctly exported (same as Jenkins creds). That does not happen:

See gerritHttpPassword

gerritFrontEndUrl: "https://eu-gerrit-1.euhpc.arm.com/"
gerritHostName: "eu-gerrit-1.euhpc.arm.com"
gerritHttpPassword: "****"
gerritHttpUserName: "jenkins"
gerritUserName: "jenkins

If we apply that config, it overwrites as literals.

In case this is possible, can you advice how we could workaround this limitation?

---

Originally reported by caipers, imported from: Export configuration as code for rest api key not supported

• assignee: rsandell
• status: Open
• priority: Major
• component(s): gerrit-trigger-plugin
• resolution: Unresolved
• votes: 0
• watchers: 1
• imported: 2025-12-07

Raw content of original issue

We have to use Gerrit REST API due to Sonarqube requirements. We also use jenkins configuration as code for our jenkins config. However, we would like to keep the REST API key (protected, same as Jenkins secrets), so I would expect when exporting the config, the rest API key would be correctly exported (same as Jenkins creds). That does not happen:

See gerritHttpPassword

gerritFrontEndUrl: "https://eu-gerrit-1.euhpc.arm.com/"
gerritHostName: "eu-gerrit-1.euhpc.arm.com"
gerritHttpPassword: "****"
gerritHttpUserName: "jenkins"
gerritUserName: "jenkins


If we apply that config, it overwrites as literals. 
In case this is possible, can you advice how we could workaround this limitation?