Skip to content

Rename remaining Akka* identifiers to Pekko* in amber Scala sources #4948

@Yicong-Huang

Description

@Yicong-Huang

Task Summary

The project migrated from Akka to Pekko, but several internal Scala identifiers still carry the Akka prefix even though they wrap Pekko APIs. Rename them so the source matches the runtime:

  • AkkaConfigPekkoConfig (common/config/.../config/AkkaConfig.scala, with akkaConfig method → pekkoConfig)
  • AkkaActorServicePekkoActorService (amber/.../architecture/common/AkkaActorService.scala)
  • AkkaActorRefMappingServicePekkoActorRefMappingService (same package)
  • AkkaMessageTransferServicePekkoMessageTransferService (same package)
  • Method/parameter names: akkaConfig, akkaActorServicepekkoConfig, pekkoActorService

Inventory across 26 .scala files: AkkaActorService ×20, akkaConfig ×17, AkkaActorRefMappingService ×17, AkkaMessageTransferService ×7, akkaActorService ×4, AkkaConfig ×3. No string-literal config keys are affected (cluster.conf already uses pekko.*); pure Scala rename. The intentional "akka" comment in DeployStrategiesSpec.scala (which contrasts pekko vs akka address strings) stays.

Task Type

  • Refactor / cleanup

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No fields configured for Task.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions