You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I have this 800 line JSON of an AWS MediaConvert job that I like to use in my Java applications. More specifically, I like to load it, edit the input and output file parameters and send it to AWS as a command.
With the version 1 client I could just use a Jackson ObjectMapper to read the JSON into a CreateJobRequest and send that. With version 2 there is now this builder-thing going on where all the generated actual request model classes are immutable and have an associated generated builder class.
Is there any way I can still load the JSON file, change a few things and use it as a request to AWS MediaConvert while still using the Credentials Provider Chain of this library?
While I'm at it, we are deploying our backend to AWS Lambda using Snapstart, and I was thinking it would probably generally be nice if there was some lightweight version of the AWS Java SDK that just handles authentication and requires the user to supply request payloads as JsonNodes or similar instead of having a trillion generated classes to represent all parameter models of all available operations. The same would go for the responses of course.
If there is something like this, I'd really like to know. If there isn't, I think this would be a huge advantage when using AWS Lambda Snapstart. In our backend function that we upload to Lambda, AWS client libraries would make up more than 15 MB. I already pull out the native executables for unused platforms from the aws-crt dependency to reduce binary size, so it is actually less, but I still think it would be nice to have a library that is way below 1 MB without hacky scripts, even if it means assembling the requests without static typing.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
So I have this 800 line JSON of an AWS MediaConvert job that I like to use in my Java applications. More specifically, I like to load it, edit the input and output file parameters and send it to AWS as a command.
With the version 1 client I could just use a Jackson ObjectMapper to read the JSON into a CreateJobRequest and send that. With version 2 there is now this builder-thing going on where all the generated actual request model classes are immutable and have an associated generated builder class.
Is there any way I can still load the JSON file, change a few things and use it as a request to AWS MediaConvert while still using the Credentials Provider Chain of this library?
While I'm at it, we are deploying our backend to AWS Lambda using Snapstart, and I was thinking it would probably generally be nice if there was some lightweight version of the AWS Java SDK that just handles authentication and requires the user to supply request payloads as JsonNodes or similar instead of having a trillion generated classes to represent all parameter models of all available operations. The same would go for the responses of course.
If there is something like this, I'd really like to know. If there isn't, I think this would be a huge advantage when using AWS Lambda Snapstart. In our backend function that we upload to Lambda, AWS client libraries would make up more than 15 MB. I already pull out the native executables for unused platforms from the aws-crt dependency to reduce binary size, so it is actually less, but I still think it would be nice to have a library that is way below 1 MB without hacky scripts, even if it means assembling the requests without static typing.
Beta Was this translation helpful? Give feedback.
All reactions