Skip to content

aptlyctl improvements #19

@rickysarraf

Description

@rickysarraf

Descripiton

As a user/infra admin, I'd like to have comprehensive tooling in place when dealing with the infrastructure.

In the scope of infrastructure, we heavily rely on the aptly repository management and publishing tool. Given the structure of our infrastructure, we expect our users to only make use of the aptlyctl tool for interaction and house keeping tasks of the aptly server.

As such, it becomes imperative to have the aptlyctl functionality be close to that of aptly. At least, for the interaction and house keeping use case. Ultimately, it is to ensure that an admin isn't required to gain access to the aptly backend for day to day chores.

For example, the aptly package feature is equally important. To query the server for list of available packages, regex them, and then a follow-up operation like delete.

@ aptly package -h
aptly package - operations on packages

Commands:

    search      search for packages matching query
    show        show details about packages matching query

Use "package help <command>" for more information about a command.


Options:
  -architectures="": list of architectures to consider during (comma-separated), default to all available
  -config="": location of configuration file (default locations are /etc/aptly.conf, ~/.aptly.conf)
  -db-open-attempts=10: number of attempts to open DB if it's locked by other instance
  -dep-follow-all-variants: when processing dependencies, follow a & b if dependency is 'a|b'
  -dep-follow-recommends: when processing dependencies, follow Recommends
  -dep-follow-source: when processing dependencies, follow from binary to Source packages
  -dep-follow-suggests: when processing dependencies, follow Suggests
  -dep-verbose-resolve: when processing dependencies, print detailed logs
  -gpg-provider="": PGP implementation ("gpg", "gpg1", "gpg2" for external gpg or "internal" for Go internal implementation)

Acceptance Criteria

  • Make an assessment of the features in aptly that should be made available in aptlyctl
  • All required functionality is available in the aptlyctl tool

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions