Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

0.39 release configuration property changes #6837

Closed
SimiHunjan opened this issue May 30, 2023 · 1 comment
Closed

0.39 release configuration property changes #6837

SimiHunjan opened this issue May 30, 2023 · 1 comment
Milestone

Comments

@SimiHunjan
Copy link
Contributor

SimiHunjan commented 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 (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

@SimiHunjan SimiHunjan changed the title 0.39 release configuration property changes 0.39 release configuration property changes May 30, 2023
@SimiHunjan SimiHunjan added this to the v0.39 milestone May 30, 2023
@david-bakin-sl
Copy link
Member

david-bakin-sl commented May 30, 2023

contracts.maxNumWithHapiSigsAccess=0 for all environments. (Cherry pick PR #7055 merged.)

@poulok poulok closed this as completed Nov 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants