Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

cf logs add support for manifest files

Aperta
#2,143 2 commenti 2 reazioni 1 assegnatario Vedi su GitHub

@gururajsh ci sta già lavorando.

Dal 20/9/2024.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

feature-request

Please provide details on the following items. Failure to do so may result in deletion of your feature request.

What's the user value of this feature request?
A quick way to tail the logs without needing to add the app name, enabling faster development, more reliably picking up the name of the app you pushed with and easier scripting

Who is the functionality for?
Developer productivity

How often will this functionality be used by the user?
Daily

Who else is affected by the change?
Net addition

Is your feature request related to a problem? Please describe.
cf logs <APP_NAME> is a pain to script and a bit slow to type out.
It would be great if we could do cf push and have it take the default manifest as it does for cf push

Describe the solution you'd like
cf logs uses the same logic as cf push , checking for a default manifest.yml or -f to take a custom named manifest.yml file

Describe alternatives you've considered
I use the below bat script to quick build/deploy but it doesnt work if the dir name is different from manifest. It might be possible to improve and parse the manifest file to extract the push name but it would be great if it was supported with the same support cf push has.
`@echo on
CALL gradlew clean build -x test
for %%I in (.) do set CurrDirName=%%~nxI
echo %CurrDirName%

CALL cf push
CALL cf logs %CurrDirName%`

Lingua principale
Go
Stelle
1.9k
Fork
990
Merge medio
1g 7h
PR unite (30g)
8

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di cloudfoundry/cli

Tutte le issue di cloudfoundry/cli

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.