nextcloud

func CancelMigration ¶

func CancelMigration(
	ctx context.Context,
	inst *instance.Instance,
	migrationID string,
	rmq rabbitmq.Service,
) error

CancelMigration validates the request and publishes a cancel command. It intentionally does NOT mutate the tracking document: the terminal state transition is owned by the migration service so there is a single writer for it.

The diagnostic logger is pulled from ctx via logger.FromContext so the caller can attach its request-scoped fields (migration_id, etc.) once with logger.WithContext rather than threading an extra parameter.

Error contract, in priority order, so callers can map via errors.Is:

• ErrMigrationNotFound: no tracking doc with this id on the instance.
• ErrMigrationAlreadyTerminal: the migration has already reached a terminal state (completed, failed, or canceled).
• ErrMigrationBrokerUnavailable: the RabbitMQ publish failed. Unlike trigger, the tracking doc is NOT marked failed: a cancel publish failure does not invalidate a migration that is already running. The user retries, or the migration finishes normally.
• any other error: treat as an internal server failure.

func DeleteMigrationSource ¶

func DeleteMigrationSource(
	ctx context.Context,
	inst *instance.Instance,
	migrationID string,
) error

DeleteMigrationSource removes the Nextcloud content ingested by the given migration, then empties the user's trashbin so the migrated bytes stop counting against quota.

SourcePath == "/" enumerates the WebDAV home and deletes each top-level child: Nextcloud refuses DELETE on the home itself with 403, so a single call would fail. An empty SourcePath is treated as "/" to match legacy docs predating source_path persistence.

Error contract (priority order, for errors.Is mapping):

• ErrMigrationNotFound, ErrMigrationNotDeletable, ErrMigrationSourceAlreadyDeleted, ErrNextcloudAccountMissing: state gates.
• webdav.ErrInvalidAuth: stored credentials rejected (401/403).
• ErrNextcloudUnreachable: any other Nextcloud-side failure.

func EnsureAccount ¶

func EnsureAccount(inst *instance.Instance, ncURL, login, password, userID string) (string, error)

EnsureAccount upserts the single Nextcloud account for the instance and returns its id. If an account already exists, its auth block and webdav_user_id are rewritten with the given values regardless of what they were before — this is the keyed-by-type policy that keeps the Settings UI free of orphans at the cost of multi-account support. The password is encrypted at rest before persistence.

func FetchUserIDWithCredentials ¶

func FetchUserIDWithCredentials(ctx context.Context, nextcloudURL, username, password string) (string, error)

FetchUserIDWithCredentials probes the OCS cloud/user endpoint and returns the user ID, or webdav.ErrInvalidAuth if the credentials are rejected. The logger used for diagnostics is pulled from ctx via logger.FromContext, so callers should attach a request-scoped logger with logger.WithContext before calling.

https://docs.nextcloud.com/server/latest/developer_manual/client_apis/OCS/ocs-api-overview.html

func FindNextcloudAccount ¶

func FindNextcloudAccount(inst *instance.Instance) (*couchdb.JSONDoc, error)

FindNextcloudAccount returns the unique Nextcloud account for the given instance, or (nil, nil) if none exists yet. By design there is at most one account with `account_type: "nextcloud"` per instance: the migration trigger endpoint overwrites the existing account on every call so a retry with a corrected password or a different login does not leave orphaned docs the Settings UI cannot surface.

If multiple legacy nextcloud accounts exist (left over from when the konnector flow kept one account per (url, login) pair), the function returns the first one scanned. Newly-triggered migrations will update that single doc; the rest stay in the database untouched until a real cleanup is wired up. A linear scan is cheaper than maintaining a Mango index because the per-instance account count is tiny.