Adds a new completion state to the deployer

[finefuture]

What is the purpose of the change

Publish started event after all action done.

before:

after:

Brief changelog

Verifying this change

Checklist

• Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
• Each commit in the pull request should have a meaningful subject line and body.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
• Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
• Add some description to dubbo-website project if you are requesting to add a feature.
• GitHub Actions works fine on your own branch.
• If this contribution is large, please follow the Software Donation Guide.

[finefuture]

Adjust dubbo-samples in pr: apache/dubbo-samples#1015

[AlbumenJ]

Change the event order might not a good idea in 3.2.x. Some users have depended on this order to export or refer services.

[finefuture]

Change the event order might not a good idea in 3.2.x. Some users have depended on this order to export or refer services.

It might be better to add some other events to implement this functionality for the user.For example, ModuleReadyEvent.

[AlbumenJ]

Change the event order might not a good idea in 3.2.x. Some users have depended on this order to export or refer services.

It might be better to add some other events to implement this functionality for the user.For example, ModuleReadyEvent.

Yes, and we can make it in 3.3.x.

[AlbumenJ]

Change the event order might not a good idea in 3.2.x. Some users have depended on this order to export or refer services.

It might be better to add some other events to implement this functionality for the user.For example, ModuleReadyEvent.

I think add some newly events would be a better option.

[finefuture]

Change the event order might not a good idea in 3.2.x. Some users have depended on this order to export or refer services.

It might be better to add some other events to implement this functionality for the user.For example, ModuleReadyEvent.

I think add some newly events would be a better option.

How about adding a new state, like completion.

[AlbumenJ]

Change the event order might not a good idea in 3.2.x. Some users have depended on this order to export or refer services.

It might be better to add some other events to implement this functionality for the user.For example, ModuleReadyEvent.

I think add some newly events would be a better option.

How about adding a new state, like completion.

ok

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
4 Code Smells

0.0% Coverage
0.0% Duplication