The auth object is added to the action meta object just in time for passing to the transporter. This is make sure secrets don't spill into the mutation pipelines.
But sometimes we'll need the auth object in mutations, e.g. when credentials need to be included in the body of a SOAP request. In these cases there should be an option to include it earlier, like authInData. This will go well together with the authAsQuery options from the http transporter, that signals to the transporter that the auth should be included in the query. authInData would also tell the transporter to not include it headers.
The
authobject is added to the actionmetaobject just in time for passing to the transporter. This is make sure secrets don't spill into the mutation pipelines.But sometimes we'll need the
authobject in mutations, e.g. when credentials need to be included in the body of a SOAP request. In these cases there should be an option to include it earlier, likeauthInData. This will go well together with theauthAsQueryoptions from the http transporter, that signals to the transporter that the auth should be included in the query.authInDatawould also tell the transporter to not include it headers.