Hello community, I encountered a strange issue whereby config repositories don't seem to work properly when we try to supply the password via a secret instead of directly in the config repo config. The connection test succeeds, so the system is fetching the password from the secret at that point, but once saved, the config repo fails to parse.
The error message (URL redacted) I see in the UI is: There was an error parsing this configuration repository: MODIFICATION CHECK FAILED FOR MATERIAL: URL: HTTPS://DEV.AZURE.COM/ORGANIZATION/TEAMPROJECT/_GIT/SANDBOX-JASONS, BRANCH: GOCD-PIPELINE-TEST NO PIPELINES ARE AFFECTED BY THIS MATERIAL, PERHAPS THIS MATERIAL IS UNUSED. Failed to load pipelines defined in this repository: There was an unknown error performing the operation. Possible reason (Not Found) The GoCD server log shows the following warning: 2024-10-18 10:47:01 jvm 1 | 2024-10-18 14:47:01,263 WARN [143@MessageListener for ConfigMaterialUpdateListener] ConfigMaterialUpdateListener:65 - [Config Material Update] Cannot update configuration part because material update has failed. Reason: When I switched from using a secret to directly supplying the password via the UI, the configuration repository started working as intended. I'm reasonably certain that this is a bug, but wanted to check with the community to confirm that using secrets in this way is supposed to be a supported use-case. Any thoughts or guidance would be appreciated. Regards, Jason Smyth -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/DM6PR16MB36715673328A38D68EA7AE8ECF402%40DM6PR16MB3671.namprd16.prod.outlook.com.
