Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Do not escape the object name in the fs backend #1017

Merged
merged 3 commits into from Dec 28, 2022
Merged

Do not escape the object name in the fs backend #1017

merged 3 commits into from Dec 28, 2022

Commits on Dec 23, 2022

  1. Do not escape the object name in the fs backend 

    Now fake-gcs-server implicitly creates parent directories when creating an
object /foo/bar/baz.  This allows creating paths longer than NAME_MAX (256) and
interoperating with existing filesystems.  This approach does not allow some
kinds of objects to exist, e.g., /foo/ with a non-zero object size, although
these should be rare.
    @gaul
    gaul committed Dec 23, 2022
    Configuration menu
    Copy the full SHA
    a0e528e View commit details
    Browse the repository at this point in the history

Commits on Dec 28, 2022

  1. Use filepath.Rel to derive the object name from the path

    @fsouza
    fsouza committed Dec 28, 2022
    Configuration menu
    Copy the full SHA
    89ff764 View commit details
    Browse the repository at this point in the history

  2. internal/backend/fs: fix usage of filepath.Rel

    @fsouza
    fsouza committed Dec 28, 2022
    Configuration menu
    Copy the full SHA
    654b0a7 View commit details
    Browse the repository at this point in the history