Skip to content

[Docker Hub] Provide a direct/synchronous download option for the organization members CSV export #920

Description

@bmdockersupport

Tell us about your request

Provide a way to obtain an organization's members CSV without the asynchronous email step — either a direct download in the organization member list as before, or an organization-level setting to choose synchronous download.

Which service(s) is this request for?

Docker Hub / Docker Home — organization member management.

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?

Organizations that collect member lists for software asset management, license reconciliation, and compliance reporting typically run this export on a schedule, unattended.

The export recently moved to asynchronous delivery: initiating it emails a download link to the organization owner rather than returning the file. Any unattended process that previously downloaded the CSV now has to receive email, parse it for a link, and follow that link to retrieve the file. That means standing up a mail integration and handling credentials for an owner's mailbox in order to fetch what is otherwise a simple periodic report.

Are you currently working around the issue?

GET /v2/orgs/{org_name}/members/export still returns the CSV body directly and works with an organization access token, so automation can be moved onto the API. That is the right long-term path.

It isn't a drop-in replacement for an existing portal-based job, though. Moving to it requires design, security review for the token handling, development, and testing before it can go into production — so teams whose existing flow broke have no direct option in the interim.

Additional context

Related to the earlier member export requests, #316 and #401, which delivered the export itself. This request is narrower: it concerns the delivery mechanism, not the data.

Asynchronous delivery makes sense for very large organizations, where generating the report inline was unreliable. A per-organization setting, or a size threshold above which delivery falls back to email, would preserve that benefit while letting smaller organizations keep the direct download their tooling depends on.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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