cf service --params doesn't comply with openservicebrokerapi Fetch Service Instance
@a-b ya está trabajando en esto.
Desde el 6/9/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.
Describe the bug and the command you saw an issue with
What: Fetch service instance details via cf CLI
Why: Implementing the functionality to offer to our stakeholders
What happened
In our service broker, we have implemented the openservicebrokerapi Fetch Service Instance endpoint in order to be able to retrieve the parameters specified in an existing service instance. Once the broker was deployed with the code changes, we have tried to fetch the parameters of a service instance via cf service <service> --params (as cf service <service> doesn't return this information). The command failed with a custom error, coming from our broker, saying that the plan ID was not provided. When checking the logs of the broker app (cf logs <broker-app> --recent) we have spotted that the GET command executed against our broker does not include any of the expected query parameters, specified by the openservicebrokerapi Fetch Service Instance. The command looked like GET /v2/service_instances/<instance-id>, instead of GET /v2/service_instances/<instance-id>?service_id=<service-id>&plan_id=<plan-id>.
When checking the broker logs for execution of cf delete-service <service> command (which we support for some time now), we can see that the command includes the query parameters, expected by openservicebrokerapi Delete Service Instance. This leads to the conclusion that there is an inconsistency of the support for query parameters between the different cf commands.
Expected behavior
- To execute with query parameters, as defined in the openservicebrokerapi Fetch Service Instance
- To receive the parameters of the service instance
Exact Steps To Reproduce
Steps to reproduce the behavior; include the exact CLI commands and verbose output:
- Have a broker, implementing openservicebrokerapi Fetch Service Instance and Create Service Instance
- Create a service instance via cf cli:
cf create-service <offering> <plan> <service> -c <config-file> - Run
cf service <service> --params - See error
Provide more context
- Mac OS Ventura 13.5
- zsh
- cf cli version: 8.7.1+9c81242.2023-06-15
- 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
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 60/100
github/gh-aw-mcpg#13748 ·
-
agentic-workflows
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
googleapis/librarian#7670 · 2 comentarios ·