Closed checketts closed 6 years ago
Where does key=sample.key
come from?
It comes from the config repo. In this example configServer-test.yml
in our Git backed repo.
You didn't show the sample.key
in configServer-test.yml
(I see only envsecrets.nightly1_v1
). It looks like you have another (mouldy) {cipher}
somewhere else, maybe in application.properties
locally?
Sorry now I understand the question about sample.key
, I apologize for the confusion the value in the stack trace was envsecrets.nightly1_v1
. I had merely cleaned up the stack trace.
I don't think this is a moldy {cipher}
since the only change is to upgrade the spring cloud dependency. (Did you mean a moldy encrypt.key
?)
I have config files I encrypted years ago and they still work with the latest config server, so I can't reproduce this issue. The most likely explanation for that error is that you used a different secret to encrypt (not a different version of Spring Cloud). Can you come up with a sample with a plaintext secret that fails in this way?
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.
Our config server is in bootstrap mode (
spring.cloud.config.server.bootstrap: true
)Example
configServer-text.yml
contents:That value is consumed by the config server itself. This seems pertinent to the bug.
When we hit the
refresh
endpoint our config server server was able to parse it in. In preparation for upgrading to Spring Boot 1.4 I realized we hadn't upgraded off the milestone release to the final release yet. However upon upgrading we noted this error when we call therefresh
endpoint: