FIX: Gap Of Uploading The Same File Key Twice
Build, Push and Deploy CMS / build-push-deploy (push) Successful in 2m19s
Build, Push and Deploy CMS / build-push-deploy (push) Successful in 2m19s
This commit is contained in:
@@ -63,8 +63,8 @@ Black-box BDD covering the video upload feature: its own Go module importing
|
||||
nothing from `cms/`, talking to a running service over HTTP only, so the same
|
||||
scenarios run against compose and against a deployed environment. Skips (does
|
||||
not fail) when nothing is serving. Uploading is a plain `PUT` to the presigned
|
||||
URL, no AWS SDK. Scenarios tagged `@known-gap` deliberately pin current
|
||||
behaviour that differs from the documented contract — see `tests/README.md`.
|
||||
URL, no AWS SDK. Scenarios can be tagged `@known-gap` to pin current behaviour
|
||||
that differs from the documented contract — see `tests/README.md`.
|
||||
|
||||
Note compose starts `cms` in server mode only: the migrate container exists in
|
||||
the ECS task definition, not in `docker-compose.yml`, so a freshly created
|
||||
|
||||
Reference in New Issue
Block a user