Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Sep 28 2019 16:50
    p4tin synchronize #204
  • Sep 28 2019 16:50

    p4tin on use_go_modules

    Use Go Modules and use Gothub A… (compare)

  • Sep 28 2019 16:32
    p4tin synchronize #204
  • Sep 28 2019 16:32

    p4tin on use_go_modules

    Use Go Modules and use Gothub A… (compare)

  • Sep 28 2019 16:14
    p4tin synchronize #204
  • Sep 28 2019 16:14

    p4tin on use_go_modules

    Use Go Modules and use Gothub A… (compare)

  • Sep 28 2019 16:12
    p4tin synchronize #204
  • Sep 28 2019 16:12

    p4tin on use_go_modules

    Use Go Modules and use Gothub A… (compare)

  • Sep 28 2019 16:08
    p4tin synchronize #204
  • Sep 28 2019 16:08

    p4tin on use_go_modules

    Use Go Modules and use Gothub A… (compare)

  • Sep 28 2019 16:06
    p4tin synchronize #204
  • Sep 28 2019 16:06

    p4tin on use_go_modules

    Use Go Modules (compare)

  • Sep 28 2019 16:02
    p4tin opened #204
  • Sep 28 2019 16:02

    p4tin on use_go_modules

    Use Go Modules (compare)

  • Sep 28 2019 16:01

    p4tin on use_go_modules

    (compare)

  • Sep 28 2019 15:54

    p4tin on master

    Update go.yml (compare)

  • Sep 27 2019 20:05
    mbklein commented #202
  • Sep 27 2019 18:18
    p4tin commented #202
  • Sep 27 2019 17:45
    mbklein commented #202
  • Sep 27 2019 17:37
    mbklein opened #203
Pascal Voitot
@mandubian
Result of subscription: Failure(com.amazonaws.AmazonServiceException: Unable to unmarshall error response (Bad Request) (Service: AmazonSQS; Status Code: 400; Error Code: 400 Bad Request; Request ID: null))
Pascal Voitot
@mandubian
thks
Paul Fortin
@p4tin
It does seem to be recosnizing the AWS command that you sent to it the 400 Bad Request is only returned when a command is not recognized - can you send me the scala code you use to Subscribe so I can test on my end?
And definately open an Issue on GIthub as well
Pascal Voitot
@mandubian
@p4tin I should extract code from our codebase which is huge...
Should the version of SDK that I use work with your code?
Paul Fortin
@p4tin
Yes it should if not i will fix it to work :)
Paul Fortin
@p4tin
@mandubian - I just redid my java tests with your aws library version and all passed - I can send you my gradle project if you want to see that
I did it in intellij but I think you can do it in any IDE or no idea. I can’t repeat in scala but the library is identical so it should work
Also from your exceptions I would make sure your jackson dependancies are compatible with the awe-java-sdk
Here are my gradle dependancies -
dependencies {
testCompile group: 'junit', name: 'junit', version: '4.11'
compile group: 'com.amazonaws', name: 'aws-java-sdk', version: '1.10.52'
runtime group: 'com.amazonaws', name: 'aws-java-sdk', version: '1.10.52'
}
Pascal Voitot
@mandubian
Thank for testing, I'll check that!
Our project is quite huge so it's hard
to be sure from where it comes :)
I just wanted to have a local SQS/SNS simulator to run local tests
Paul Fortin
@p4tin
I really hope you get it working :)
Pascal Voitot
@mandubian
woudl be really cool actually :)
because for developers, having to depend on external services is a real pain
Paul Fortin
@p4tin
you can also try: https://github.com/unbounce/yopa but it is slow and harder to configure in my opinion :) but I am biased!
Pascal Voitot
@mandubian
For information, we have succeeded in using GoAws, finally :D
The issues were that:
  • setMessageVisibility isn't supported
  • AwsAccountId is replaced by queue in SQS
Thanks for that great tool, it will help us a lot :)
Paul Fortin
@p4tin
Glad it can help Pascal if you want a feature implemented just ask.
Mark Meany
@mmeany
Hi @p4tin and thanks for the tool which I have been using with some success. I have been using the Docker version and am struggling to get it to read a config file I provide. Basically all attempts fail. I can manually create the queues and topics using the awscli, but would like to simply add a goaws.yml file in our code repo for testing. I have looked at the docker-compose.yml file in the repo, this mounts a volume at /config, but connecting to the image there is a folder /conf and that looks like the one being used. If I mount to /config the configuration is ignored and the one in /conf is used still. If I mount to /conf it looks like it is still ignored as I get no topics or queues. Any tips would be appreciated.
Paul Fortin
@p4tin
Hey @mmeany thanks for the nice words let me give this a test I have tried it before running docker run but I do not think I ever tried with docker-compose but it should work the same.
Paul Fortin
@p4tin

There was a small error in the docker-compose.yml that I am fixing now there should be a new docker image up on docker hub in a few mins. Make sure you put your new goaws.yaml file in a directory that you will mount in the image as /conf so if you have a config directory where then yaml file lives you should have:

 volumes:
      - ./config:/conf

and the file should get picked up

New docker image uploaded
Paul Fortin
@p4tin
BTW easier than usign the ‘awscli’ is to use the postman collection that I have a link to in the README.md - you can do anything from there and it’s easier to use than awscli
Paul Fortin
@p4tin
@tomasbartkus - hello
Mark Meany
@mmeany
Just wanted to report back that have had success with latest docker image. Many thanks and keep up the good work.
Mark Meany
@mmeany
Maybe worth adding to the README.md the extra for Run (Docker Version):
docker run -d --name goaws -p 4100:4100 -e "PUBLICHOST=localhost" -v $(pwd)/conf:/conf pafortin/goaws
Paul Fortin
@p4tin
new version of goaws (bug fix + update to go1.7) — docker image updated as well
Marcos
@marcrosis
hey
I'm having some issues here
I set up a SNS -> SQS subscription
If I publish an event to the SNS topic I receive messages to the SQS queue
but they don't have subject and body
aws --endpoint-url http://localhost:4100 sns subscribe --protocol sqs --topic-arn $hydrate_sns_arn --notification-endpoint $hydrate_sqs_name
this is my subscription
this is how i'm publishing
aws --endpoint-url http://localhost:4100 sns publish --topic-arn arn:aws:sns:local:000000000000:hydrate --message 'ajkdehgakjhgdhksahgdkhgasjdgasjhdgjahsgdjhas' --subject '{"asdas":"asdasdas"}' --message-structure json
Marcos
@marcrosis
:cry:
Daniel P. Zepeda
@duskhacker
I want to use goaws with github.com/aws/aws-sdk-go (the official Go SDK). Do you know if there is an easy way to configure aws-sdk-go to use goaws? I've looked around in the code a bit, but haven't found anything that exactly fits that need. I've also considered simply updating my /etc/hosts file to point amazonaws.com to localhost. However 1) I'm unsure if amazonaws.com is the right one, the only one to redirect, and 2) I'd really rather configure the library than mess with my system.
Paul Fortin
@p4tin
@duskhacker - Sorry it took so long to get back to you. If you have not solved your issue maybe this will help... The Key is to provide the endpoint to use instead of the defaults which is amazonaws. You can do this with this snippet of code (this is SNS but it's the same for SQS):
awsHost := "localhost"
awsPort := "4100"
awsConfig := &aws.Config{
    Region: aws.String("LOCAL"),
    Endpoint: &fmt.Sprintf("http://%s:%s", awsHost, awsPort),
}
aws_session, _ := session.NewSession(awsConfig)
sns_svc = sns.New(aws_session)
Scott Lindsey
@scott-r-lindsey
Hostname support seems to be broken?
# aws \
    --endpoint-url http://my-docker-container:4100 \
    sns \
    create-topic \
    --name some-cool-topic

# aws --endpoint-url http://my-docker-container:4100 sns list-topics
{
    "Topics": []
}
I can't figure out how to get topics to stick unless I go in as "localhost" which works
Scott Lindsey
@scott-r-lindsey
I've resolved this. The problem was that the older version of the AWS client I was using within the container was failing to parse the output from goaws, while the AWS client I was using on my local machine was having no difficulty, and this appeared to indicate that accessing via localhost was giving a different result than accessing the same endpoint via a hostname. Cheers!
Zach Schultz
@zachschultz
Hey there, any advice on setting the repo up on a Mac environment to contribute? I'm not sure how to get all the needed dependencies and use the makefile
Laurynas Tretjakovas
@n3ziniuka5
Hey @p4tin , could you update the docker image? Was debugging why sending messages in batch wasn't working, then found this p4tin/goaws#141. So it is resolved, but the docker image hasn't been updated.