cf login with certain options results in rename Access is denied error message
@a-b ya está trabajando en esto.
Desde el 1/10/2024.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Please fill out the issue checklist below and provide ALL the requested information.
- I reviewed open and closed github issues that may be related to my problem.
- I tried updating to the latest version of the CF CLI to see if it fixed my problem.
- I attempted to run the command with
CF_TRACE=1to help debug the issue. - I am reporting a bug that others will be able to reproduce.
- [ ] If this is an issue for the v7 beta release, I've read through the official docs and the release notes.
Describe the bug and the command you saw an issue with
Trying to run cf login -a <api url> -o <org> -s Dev --sso but it does not work and instead returns Error writing config: rename C:\Users\<username>\.cf\temp-config696932450 C:\Users\<username>\.cf\config.json: Access is denied.
What happened
C:\Users\<username>\.cf\temp-config696932450 and C:\Users\<username>\.cf\config.json are left on file system. Inspecting config.json it looks incomplete. Manually moving temp-config696932450 to config.json appears to result in it working until next login.
Expected behavior
This command logs in without errors
To Reproduce
- Run
cf login -a <api url> -o <org> -s Dev --sso - Enter Temporary Authentication Code
- See error
Provide more context
- Windows 10
cf loginworked in this way through 6.46.1. Starting with 6.47.1 this no longer works.- note 6.47 refactored how
cf loginworks which probably broke this - see https://github.com/cloudfoundry/cli/releases/tag/v6.47.0 - Git bash, PowerShell, CMD... all same error
- still broken in 6.51.0
- API version: 3.66.0
- I have confirmed with multiple users they have same issue
- I have tried to catch what might be locking
config.jsonusing Process Explorer, Resource Monitor, etc. but none seem to catch anything lockingconfig.json
- Lenguaje dominante
- Go
- Estrellas
- 1.9k
- Forks
- 990
- Merge medio
- 1 d 7 h
- PR fusionados (30 d)
- 8
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de cloudfoundry/cli
-
Dificultad 4/5 3-5 días Aptitud para principiantes 52/100
cloudfoundry/cli#3866 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
cloudfoundry/cli#3863 · 2 comentarios ·
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 45/100
cloudfoundry/cli#3851 · 1 comentario · 1 reacción ·
-
Add zsh shell completion Abierto
Dificultad 3/5 1-2 días Aptitud para principiantes 62/100
cloudfoundry/cli#3794 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 48/100
cloudfoundry/cli#3787 · 1 comentario ·
Todos los issues de cloudfoundry/cli
Issues similares
-
nix: vendorHash is outdated Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
-
Bob Shell support Abiertoenhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
santhosh-tekuri/jsonschema#276 ·