trailing slash required in bucket_prefix about aws-transit-vpc HOT 3 OPEN

Thank you for the feedback. We updated the documentation to include the requirement that the bucket prefix end with a trailing slash.

from aws-transit-vpc.

I saw your fork with a "AllowedPattern" update to the template. I really like this approach beyond just adding information to the documentation. However, looking at your example:
"AllowedPattern": "^[a-z0-9A-Z][a-z0-9A-Z/]+/$"

I believe this will require a prefix that starts with one letter or number and contains at least one more letter, number, or forward slash, followed by another '/'

This precludes "no" prefix (just a '/') as well as an prefix with a dash, underscore, or period in it. What do you think of the following pattern instead?

"AllowedPattern": "^[a-z0-9A-Z_/-./]*/$"

Which requires a trailing '/', but allows letters, numbers, dashes, underscores, periods, or forward slashes. Are there other characters we would also want to include?

from aws-transit-vpc.

@stevemorad yep, that seems to resolve it neatly as it requires the trailing slash. I didn't have time to finish my implementation to my satisfaction :)

from aws-transit-vpc.