Skip to content
Snippets Groups Projects
  1. May 23, 2024
  2. May 22, 2024
  3. May 16, 2024
  4. May 15, 2024
  5. May 07, 2024
  6. Apr 26, 2024
  7. Mar 29, 2024
  8. Mar 13, 2024
  9. Feb 05, 2024
  10. Jan 30, 2024
  11. Dec 21, 2023
  12. Dec 06, 2023
  13. Dec 05, 2023
  14. Dec 01, 2023
  15. Nov 29, 2023
  16. Nov 28, 2023
    • David Douard's avatar
      Update to swh-py-template v0.1.5 · f84b27f7
      David Douard authored
      - remove sphinx-dev tox env,
      - use non-editable install of swh-docs to build the sphinx doc in tox,
      - remove (now useless) MANIFEST.in.
      f84b27f7
    • David Douard's avatar
      Remove the 'github' package extra · d5f63c82
      David Douard authored
      It's not needed any more.
      d5f63c82
    • David Douard's avatar
      Migrate to copier-base template · 7fcefc48
      David Douard authored
      This replaces the setup.py package file with pyproject.toml (keeping
      setuptools and setuptool_scm) and use an implicit namespace declaration
      for the swh namespace.
      
      Also note that due to the poor support of PEP 420 in pytest, it needs a
      pair of command line arguments to pass all tests (see tox.ini).
      7fcefc48
  17. Nov 09, 2023
  18. Sep 06, 2023
  19. Aug 03, 2023
  20. Jul 13, 2023
    • David Douard's avatar
      Fix read-access granting to the guest user in db_utils · 5bbe5cec
      David Douard authored
      It was missing a commit to actually be granted.
      Add a test for this specific behavior, making sure the guest user has
      proper permissions.
      
      Note that this will work if and only is the guest user does not inherit
      from a bunch of default permissions when created (needs a NOINHERIT).
      5bbe5cec
  21. Jul 10, 2023
  22. Jul 07, 2023
    • David Douard's avatar
      b26a668e
    • David Douard's avatar
      Make `swh db init` command work properly with the --dbname option · 89d48572
      David Douard authored
      This allows to run the command `swh db init --dname DBURI` without
      giving a configuration file while still populating the dbversion table
      in the database.
      
      Note that this may not work for all swh packages, when the postgresql
      backend for the given swh package needs more configuration entries than
      just the psql connection string.
      
      This more or less drops support for "old style" db sql init scripts:
      
      - the `swh db init` will still work for an 'old style' package (in which
        the sql init scripts do create dbversion table and initialize it) but
        will display an error message,
      - the --initial-version option has been dropped, since this made sense
        only for old style packages,
      - the test data 'cli_new' has been renamed as 'cli' (in place of the
        previous "old style" one)
      89d48572
  23. Jun 26, 2023
  24. Jun 20, 2023
  25. Jun 14, 2023
  26. Jun 13, 2023
  27. May 11, 2023
    • vlorentz's avatar
      cli: Prevent rewrapping of code blocks · 984da898
      vlorentz authored
      Before:
      
      ```
      $ swh db init -h
      Usage: swh db init [OPTIONS] MODULE
      
        Initialize a database for the Software Heritage <module>.
      
        The database connection string comes from the configuration file (see option
        ``--config-file`` in ``swh db --help``) in the section named after the
        MODULE argument.
      
        Example::
      
            $ cat conf.yml     storage:       cls: postgresql       db:
            postgresql://user:passwd@pghost:5433/swh-storage       objstorage:
            cls: memory
      
            $ swh db -C conf.yml init storage  # or     $
            SWH_CONFIG_FILENAME=conf.yml swh db init storage
      
        Note that the connection string can also be passed directly using the '--db-
        name' option, but this usage is about to be deprecated.
      ```
      
      After:
      
      ```
      $ swh db init -h
      Usage: swh db init [OPTIONS] MODULE
      
        Initialize a database for the Software Heritage <module>.
      
        The database connection string comes from the configuration file (see option
        ``--config-file`` in ``swh db --help``) in the section named after the
        MODULE argument.
      
        Example::
      
                $ cat conf.yml
                storage:
                  cls: postgresql
                  db: postgresql://user:passwd@pghost:5433/swh-storage
                  objstorage:
                    cls: memory
      
                $ swh db -C conf.yml init storage  # or
                $ SWH_CONFIG_FILENAME=conf.yml swh db init storage
      
        Note that the connection string can also be passed directly using the '--db-
        name' option, but this usage is about to be deprecated.
      ```
      984da898
    • vlorentz's avatar
  28. May 10, 2023
    • vlorentz's avatar
      config: Remove confusing magic in path handling · 2663c0a4
      vlorentz authored
      1. When passed a .yaml path (or any path with a non-whitelisted extension),
         don't read .yml instead when the .yaml exists.
         It's an extremely surprising behavior.
      
      2. If the .yaml file does not exist, it will still try alternative extensions
         in order not to break existing deployments which may rely on it, but it
         raises a warning now.
      
      3. When given a non-existing path, show an error log, but keep parsing
         it as an empty config, in order not to break existing deployments.
      2663c0a4
  29. May 02, 2023
Loading