[TIMOB-27060] Investigate potential breakage from S3 path style deprecation
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | None |
| Status | Open |
| Resolution | Unresolved |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | n/a |
| Labels | n/a |
| Reporter | Ewan Harris |
| Assignee | Ewan Harris |
| Created | 2019-05-04T17:36:02.000+0000 |
| Updated | 2019-06-12T14:37:22.000+0000 |
Description
https://forums.aws.amazon.com/ann.jspa?annID=6776
S3 is deprecating accessing S3 via
s3.amazonaws.com/<bucketname>/key in favour of <bucketname>.s3.amazonaws.com/key, I believe this will affect appc-mobilesdk-server and titaniumlib fetching the releases.json file.
cc [~cb1kenobi]
I've updated titaniumlib https://github.com/appcelerator/titaniumlib/pull/13. node-ios-device v1 references appc-node-binaries.s3.amazonaws.com, so that's good to go. node-ios-device v2 uses prebuilds and does not publish to S3.