winglang/wing

Handle duration in signedurl implementation for every cloud provider

Open

#4,280 opened on Sep 26, 2023

View on GitHub
 (5 comments) (1 reaction) (0 assignees)TypeScript (214 forks)github user discovery
good first issue🎨 sdk🐛 bug

Repository metrics

Stars
 (5,385 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

I tried this:

Implemented signedurl and realized this need to be addressed: What if the user put a duration less than the minimum or higher than maximum? see here The different cloud targets could have a different time scope, and it'll require a little bit of research.

This happened:

Currently we are not handling duration less than the minimum or higher then the maximum.

I expected this:

Need to explore the right behavior.

Is there a workaround?

No response

Component

SDK

Wing Version

No response

Node.js Version

No response

Platform(s)

No response

Anything else?

No response

Community Notes

  • Please vote by adding a 👍 reaction to the issue to help us prioritize.
  • If you are interested to work on this issue, please leave a comment.

Contributor guide

Research direction
Research the minimum and maximum duration limits for signed URLs for each supported cloud provider (AWS, Azure, GCP, etc.) and implement validation to clamp or error accordingly.
Tech stack
typescriptaws
Domain
backendcloud
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75