Menu

#99 1.11.x breaks existing S3 backend configurations

duply
closed-duplicate
nobody
None
5
2016-12-11
2016-08-21
No

I have seen #90, but I don't agree that it should be a documentation fix. The AWS credentials are essentially username and password, and have been used as TARGET_USER and TARGET_PASS for a long time. Wouldn't the "principle of least astonishment" say that there should be some code to detect whether the AWS variables are set and set them properly based on TARGET_USER/TARGET_PASS like it has been all along? I don't understand why it would break an existing/working configuration.

Error:
NoAuthHandlerFound: No handler was ready to authenticate. 1 handlers were checked. ['HmacAuthV1Handler'] Check your credentials

Tommy

Discussion

  • ede

    ede - 2016-08-22
    • status: open --> closed-duplicate
     
  • ede

    ede - 2016-08-22

    sorry that you do not concur. but it's decided and going to stay that way.

    the issue here is code maintainablility and for that reason i decided to go with the all or nothing approach. formerly i tried to simplify all backends, which became unfeasable with some new backends, so all this spaghetti code was removed and replaced by some exports in the conf file.

    it's unfortunate but rooted in the limited time i can afford on duply. sorry for the inconvenience.. ede

    PS: please don't file new bugs if a ticket exists already. thx.

     
  • Tommy McNeely

    Tommy McNeely - 2016-08-22

    Well, sir, I can certainly appreciate cleaning up code and making things more efficient, and that you have the authority to make whatever changes, however you see fit. However, when you introduce non-backwards-compatible changes, its fairly customary to make a "major" version number change, rather than a minor version change. http://semver.org/

    Have a nice day,
    Tommy

     
    • OJ User

      OJ User - 2016-08-22

      On 22.08.2016 18:09, Tommy McNeely wrote:

      Well, sir, I can certainly appreciate cleaning up code and making things more efficient, and that you have the authority to make whatever changes, however you see fit. However, when you introduce non-backwards-compatible changes, its fairly customary to make a "major" version number change, rather than a minor version change. http://semver.org/

      Have a nice day,

      had it already, thanks! i appreciate your input and will take it to heart the next time i have to make changes like that :).. thanks agn ede/duply.net

       
  • mistawac

    mistawac - 2016-12-11

    I'm receiving this error while trying to test Duply, my secret and access key are plain text in the conf file in my directory. Has the format for S3 changed?

     
  • ede

    ede - 2016-12-11

    yes.. please download duply 2.0.1 and create a new profile. find within the template conf file directions on how to export the vars needed for s3..

    ede

     

Log in to post a comment.

MongoDB Logo MongoDB