Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Support "droplet" argument for cf run-task

Abierto
#2,132 2 comentarios 0 reacciones 1 asignado Ver en GitHub

@gururajsh ya está trabajando en esto.

Desde el 20/9/2024.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

feature-request

Very small request here.

What's the user value of this feature request?
Being able to nominate a droplet at task creation time allows the user to avoid potential race condition pitfalls relating to setting the app's "current" droplet.

(See also: what the user value was for adding this possibility to the underlying v3 api at all)

Who is the functionality for?
Likely people who are using cloudfoundry in a fairly automated fashion, with frequent rolling deployments and multiple droplets.

How often will this functionality be used by the user?
Well, we're looking at using it in our pipeline for database migrations so for us it would be run as part of every new deployment.

Who else is affected by the change?
Does this feature cause a breaking change? No.

Is your feature request related to a problem? Please describe.
I think I've probably already described this, but when you have quite a lot of things going on with your app, performing a mutation to it (by setting the "current droplet") is a bit of an unnerving thing to do if you don't necessarily know all the consequences.

Describe the solution you'd like
Probably a --droplet-guid flag for cf run-task.

Describe alternatives you've considered
We're currently using cf curl. It works. But this (really neat) possibility is very undiscoverable because it's not exposed in the cli.

Lenguaje dominante
Go
Estrellas
1.9k
Forks
990
Merge medio
1 d 7 h
PR fusionados (30 d)
8

Guía de contribución

Abrir la guía de contribución

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 cloudfoundry/cli

Todos los issues de cloudfoundry/cli

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.