I have some encrypted strings in application.yml, just like
"{cipher}AQB3pYMRyzt61ANiBBUO7prB1C0NK/p3Mmv1D3IaVeDXOUNj1GxE/yTCthUNwZEMGFOJR+2Jmx/CdkUUJ6wr4w7zsA1C9JxSFUXTgNSZ3BJmgMiaeljn8jjedS/5IqyO2Nh4NqCDJ293evTCyU8vednxpuVF3qpbB+EHILEFThAukV3rzjXS/b3UiNMzsN5Gwo73tUo2akLHEamnXoNaDT/ioDwGJeGHGSP+mN95jUlhI5FqdSv9Qst+x5MzEbmTxjuju2Vir4rje4Ccp67W6CIIhu+JeWuz/lHIk3PZsQaHO+7qn7gDhKrJiCO6AEYT1Fzp+b9zRbpigH3PxQt4nlOE5FuqjDlDRR48sd76jHAY9bpLYk5od54kWiHx9CzLuy2clU7ldotJdJmpxDmVOnmB"
I don't want this property decrypted by spring cloud config server, so I add
spring.cloud.config.server.encrypt.enabled: true in my configuration.
I use spring cloud config server v1.3.0.RELEASE for a while, everything works fine.
When I upgrade to v1.3.3.RELEASE, the spring.cloud.config.server.encrypt.enabled: false seems not work any more. The server decrypted strings for me, it's not what i want.
Can you try putting spring.cloud.config.server.encrypt.enabled: true in bootstrap.properties?
@spencergibb it worked.
That's wired. Why it's not work in application.yml.
It's need to be mentioned in the document.
I think it is
Should also be documented in earlier releases (and release notes).
Closed via 8da878b
Most helpful comment
Can you try putting spring.cloud.config.server.encrypt.enabled: true in bootstrap.properties?