pjfanning opened a new pull request, #3026:
URL: https://github.com/apache/pekko/pull/3026

   Removes the old `passivate-idle-entity-after` backward-compatibility branch 
and associated internal machinery that was kept to bridge the 
pre-passivation-strategy API. `PassivationStrategySettings` and 
`withPassivationStrategy` are now stable API.
   
   ## Removed
   - `oldSettingUsed: Boolean` field from `PassivationStrategySettings` 
(classic + typed)
   - `withOldIdleStrategy(timeout)` method
   - `oldDefault(idleTimeout)` method
   - `fromSharding(shardingConfig)` method and its 
`passivate-idle-entity-after` config-key fallback branch
   - `@ApiMayChange` annotations on `PassivationStrategySettings` (class + 
companion + `apply`) and `withPassivationStrategy`
   
   ## Changed
   - `apply(config: Config)` in `ClusterShardingSettings` now reads passivation 
settings directly via 
`PassivationStrategySettings(config.getConfig("passivation"))` instead of going 
through `fromSharding`
   - `PassivationStrategySettings.apply(classic)` / `toClassic(settings)` in 
the typed module no longer thread `oldSettingUsed` through
   
   ## Migration note
   `passivate-idle-entity-after` is no longer read. Operators using this key 
must migrate to `pekko.cluster.sharding.passivation.strategy` before upgrading. 
The risk during a rolling 1.x→2.x upgrade is behavioural only (passivation 
config inconsistency across nodes during the window); there is no 
wire/serialization or binary-API breakage since `ClusterShardingSettings` is 
never serialized and all removed members were `private[pekko]`.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to