-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
send message with options #10
Conversation
Hi @samoconnor - I'm facing the same issue. Is this PR going to be merged? Any issue? |
I’ll take a look at this tomorrow, and get it in for you! |
Thanks for take care of this. We're going to use this package for a production process. |
Slowly working on bringing this package up to current standards. Do you have a timeline @tk3369 for when you are going live with your production stage? |
We are probably going live next month. We do have a slightly ugly workaround by calling |
I can definitely wrap up updating this package and getting this change in there as well in that time frame! I think looking into AWSCore.jl might also be an option as it's a more mature package. |
Closing in favour of #16 since I did not have permissions to push to this fork. |
I couldn't send message to a FIFO queue with the master code, because this type of queue requires MessageGroupId parameter.
I just proposed options... to the sqs_send_message function so it doesn't affect the usage.
Maybe there exist a smarter way to do this. No need to merge this if you have better solutions.
Thanks