macOS and Linux API versions differ from Windows

Abierto
  • ¿Algo no está bien?
#1,135 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
22/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
cli, python
Área
api, cli

Línea de trabajo

The bug is reported against the b2 CLI's key create and account authorize commands, which behave differently on macOS/Linux than on Windows. Start from the key-creation code path in the CLI and compare how capabilities are passed to the Backblaze API on each platform, then check the API version the client requests. Done means a key created on macOS/Linux authorizes successfully and appears in the web portal; the issue has four comments and no linked pull request, so ask the maintainers for direction first.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug

The b2 CLI app behaves differently on macOS/Linux than it does on Windows when creating a key.
Versions tested: Up to 4.5.1

Reproducible example:

  1. Authorize with master account.
  2. Try to create a key with the following permissions:
b2 key create --bucket my-bucket-name-here Test-Write-Only-Key-Files-1 listBuckets,readBuckets,listFiles,readFiles,writeFiles,readBucketEncryption,readBucketReplications,readBucketRetentions,readFileRetentions,writeFileRetentions,readFileLegalHolds

When attempting a b2 account authorize with the key information yields the following error:
ERROR: unable to authorize account: This request is not currently supported on API version number 2 (bad_request)

Additionally, the key is hidden from the "Application Keys" portion of the web portal.

Running the same command on the Windows version creates the correct key as expected, allows authorization, and shows itself in the web portal.

Lenguaje dominante
Python
Estrellas
638
Forks
138
Merge medio
8 h 27 min
PR fusionados (30 d)
8

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Backblaze/B2_Command_Line_Tool

Todos los issues de Backblaze/B2_Command_Line_Tool

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.