You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need a way to track configuration changes we are expecting to make for each release. These are any changes that are made to the bootstrap.properties file.
Solution
Document the expected bootstrap.properties changes for the release.
Enabled: virtualdatasource.jasperdbToMerkledb
Disabled:
Changed:
contracts.maxNumWithHapiSigsAccess=0 (from 10_000_000, has the effect of retiring the smart contracts V1 security model; only V2 security model now available - except for specific grandfathered contracts)
Removed:
Default configs that need to be updated by DevOps for the release:
Alternatives
No response
The text was updated successfully, but these errors were encountered:
SimiHunjan
changed the title
0.39 release configuration property changes0.39 release configuration property changes
May 30, 2023
Problem
We need a way to track configuration changes we are expecting to make for each release. These are any changes that are made to the bootstrap.properties file.
Solution
Document the expected bootstrap.properties changes for the release.
Enabled:
virtualdatasource.jasperdbToMerkledb
Disabled:
Changed:
contracts.maxNumWithHapiSigsAccess=0
(from10_000_000
, has the effect of retiring the smart contracts V1 security model; only V2 security model now available - except for specific grandfathered contracts)Removed:
Default configs that need to be updated by DevOps for the release:
Alternatives
No response
The text was updated successfully, but these errors were encountered: