-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
DynamoDB #1
Comments
ghost
assigned zmsmith
Feb 19, 2013
Completed. |
spulec
pushed a commit
that referenced
this issue
Nov 23, 2013
Corrected test and multipart size check
spulec
pushed a commit
that referenced
this issue
Dec 6, 2015
JackDanger
pushed a commit
that referenced
this issue
Jun 1, 2017
Bug fix for infinite loop when WaitTimeSeconds was set to 0
spulec
pushed a commit
that referenced
this issue
Oct 15, 2018
Pull latest changes from upstream (version 1.3.6)
awallace-r7
added a commit
to awallace-r7/moto
that referenced
this issue
Mar 22, 2019
…vpc to master * commit '92575f1cd7c57a8bc75308797b872d6868f9de6a': HC-7220: Add dummy responses for failing endpoints.
shmygol
added a commit
to shmygol/moto
that referenced
this issue
Nov 21, 2019
A query fails if it has a space between `begins_with` and `(`, for example: ```begins_with (getmoto#1, :1)``` Fix getmoto#1996
iainb
added a commit
to iainb/moto
that referenced
this issue
Jul 31, 2020
When using pynamodb's support for transactions it makes use of of ExpressionAttributeNames that look like #0 getmoto#1 etc. According to https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Expressions.ExpressionAttributeNames.html And when testing against dynamodb-local these work without issue, however, when testing with moto they fail.
bblommers
pushed a commit
that referenced
this issue
Jul 31, 2020
When using pynamodb's support for transactions it makes use of of ExpressionAttributeNames that look like #0 #1 etc. According to https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Expressions.ExpressionAttributeNames.html And when testing against dynamodb-local these work without issue, however, when testing with moto they fail.
spulec
pushed a commit
that referenced
this issue
Dec 4, 2020
kfrydel
added a commit
to kfrydel/moto
that referenced
this issue
Jan 15, 2025
This is a basic implementation of restore job. It supports only selected set of jobs parameters, for example, it does take into account priority, different manifest formats. It does not generate report file at the end of the job. It does not check ETag of manifest. Tests are also not implemented. Supported opertions: - creating a job - getting description of a job It is possible to change delay time for restoration using the following endpoint from the internal API: POST /moto-api/s3control/configure {"restoration_delay_in_seconds": 123}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Creating a Mock DynamoDB
The text was updated successfully, but these errors were encountered: