Enhance AssetCompute microservice to accept altText

[#1]

Request for Feature Enhancement (RFE) Summary:	Enhance AssetCompute microservice to accept altText
Use-case:	Today AssetCompute microservice, helps to upload asset. If the asset has associated `altText` or additional metadata, the code has to wait until processing complete event. And then update `altText` and metadata. If the microservice itself supports updating additional metadata to asset, can help saving second trip to update.
Current/Experienced Behavior:	No ability to update asset metadata during create
Improved/Expected Behavior:	API supports ability to update (limited) metadata during create itself.
Environment Details (AEM version/service pack, any other specifics if applicable):	AEMaaCS
Customer-name/Organization name:	SGWS
Screenshot (if applicable):
Code package (if applicable):

[#2]

@sarav_prakash Thanks for proposing this idea.

This has been reported to the engineering under the internal reference ASSETS-43675. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to Jira's status.

[#3]

@sarav_prakash not sure I understand - is the alt-text embedded on the asset that is being ingested? We have enabled a metadata input panel for asset uploads ingested from Express and Content Hub, is the ask to add Alt-text here? Based on your mention of events I can't tell if you are looking for UI or API based approach here

[#4]

Hi @alext79299363 , this is API route. No UI. I am daily importing assets from 3rd parties thru batch job. Have been using AssetCompute to ingest asset and then assets api to add altText. Only timing is bad, since I have to cache altText temp and then after asset creates, must flush into asset. This is inconvenient, asking if API can accept altTexts