Skip to content

Changes for public bucket access #37

Description

@michaelconnor00

Some customers use internal buckets or public buckets. Examples: Enexus uses a private bucket, where Mermaid uses their own bucket with public read access. The frontend handles this by evaluating the stac asset url and if it starts with s3:// it uses the fileproxy endpoint, otherwise it tries to access the url directly.

This ticket it to review and make necessary changes for these new variations with bucket asset access.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions