Change AcknowledegmentMessage interface

[KeonHee]

Description

1. instanceType json field added
   • It is necessary when another component is added to distinguish json values of invoker and controller.
2. Add test case for serde InstanceId
3. Change AcknowledegmentMessage interface
   • The AcknowledegmentMessage may not always respond to the invoker

Related issue and scope

no related issue

My changes affect the following components

• API
• Controller
• Message Bus (e.g., Kafka)
• Loadbalancer
• Invoker
• Intrinsic actions (e.g., sequences, conductors)
• Data stores (e.g., CouchDB)
• Tests
• Deployment
• CLI
• General tooling
• Documentation

Types of changes

• Bug fix (generally a non-breaking change which closes an issue).
• Enhancement or new feature (adds new functionality).
• Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

• I signed an Apache CLA.
• I reviewed the style guides and followed the recommendations (Travis CI will check :).
• I added tests to cover my changes.
• My changes require further changes to the documentation.
• I updated the documentation where necessary.

[rabbah]

hi @KeonHee can you expand on the need for this change? What components are you adding that are not "invokers" but which are sending ack messages?

[KeonHee]

hello @rabbah sorry for late reply

Yes we have a component called "scheduler" between the controller and invoker.
The scheduler is acting as a queue. So, the message that stayed in the queue too long due to lack of resources in the invoker or not is responded back to the controller.

[style95]

👍

If this is to use some methods of CommonLoadBalancer in the downstream, isn't there any other methods to be updated as well?

[style95]

LGTM