Skip to content

evaluate default_message_expire with FES consistency #4014

Description

@tomholub
// todo - rethink this. On FES, expiration is handled with S3 bucket policy regardless of this number// which is set to 180 days on buckets we manage. This number below may still be rendered somewhere// when composing, which should be evaluated.
account: {default_message_expire: 180}

check how default_message_expire affects the extension when FES is used. I suppose it's used to render a hint to the user. (and I know it's not used to decide the actual expiration)

Originally posted by @tomholub in #4013 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions