Chinmaya, You have a couple of options. You can downgrade the whole API and declare it experimental. That's done by setting the semantic version to less than 1 in the .api file. e.g. option version="0.0.1";
You can leave the API in production status, but mark those messages you believe will change in the near future as "option status="in_progress";". Or create a new set of in production messages as _2 and mark the _1 messages as deprecated (option deprecated="true";. [...] > 7. After we are done with changes 4, 5 and 6; we need to modify > foreach_vpe_api_msg macro to register the appropriate handler functions. Please use the updated auto-generated code instead of doing this manually. > Is this what we are suppose to do or is there some other way to cater the new > in-progress message? Only use in-progress, if that's really the status of the message. I.e. it's unstable. Best regards, Ole
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16823): https://lists.fd.io/g/vpp-dev/message/16823 Mute This Topic: https://lists.fd.io/mt/74894689/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
