feat: support bulk KEY=VALUE pairs for secrets and variables

[lukevmorris]

Note

Medium Risk
Adds new batch-write RPC usage and new CLI argument parsing paths for secret/variable creation; mistakes could create unintended org/repo-scoped values or reject valid input.

Overview
Adds batch APIs (CIBatchAddSecrets, CIBatchAddVariables) to create multiple CI secrets/variables in a single org- or repo-scoped request.

Updates depot ci secrets add and depot ci vars add to accept multiple KEY=VALUE arguments, validate incompatible flags (--value/--description), and route to the new batch endpoints while preserving the existing single-item interactive/flag flows.

^{Written by Cursor Bugbot for commit ae1213d. This will update automatically on new commits. Configure here.}

[graphite-app]

Validation allows empty secret values. The check len(parts) != 2 || parts[0] == "" only validates the key is non-empty, but parts[1] (the value) can be empty. A user entering FOO= would create a secret with an empty value, potentially causing production failures.

parts := strings.SplitN(arg, "=", 2)
if len(parts) != 2 || parts[0] == "" || parts[1] == "" {
    return fmt.Errorf("invalid argument %q — expected KEY=VALUE format with non-empty key and value", arg)
}

Suggested change

	parts := strings.SplitN(arg, "=", 2)
	if len(parts) != 2 || parts[0] == "" {
	return fmt.Errorf("invalid argument %q — expected KEY=VALUE format", arg)
	}
	secrets = append(secrets, &civ2.SecretInput{Name: parts[0], Value: parts[1]})
	parts := strings.SplitN(arg, "=", 2)
	if len(parts) != 2 || parts[0] == "" || parts[1] == "" {
	return fmt.Errorf("invalid argument %q — expected KEY=VALUE format with non-empty key and value", arg)
	}
	secrets = append(secrets, &civ2.SecretInput{Name: parts[0], Value: parts[1]})

Spotted by Graphite



Is this helpful? React 👍 or 👎 to let us know.