Pushing ManifestV3 with no start

Open
#1,187 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
api

Research direction

Start by comparing the pushManifest and pushManifestV3 entry points, focusing on how the no-start parameter and labels feature are handled. Confirm whether ManifestV3 can accept no-start while retaining labels support; done means the requested behavior is implemented and covered by relevant tests.

Written by the indexing model from the issue text.

Description

Hello,
Just to be sure, is it currently possible to do a pushManifestV3 with a no-start parameter? It seems that it's possible with the pushManifest method but I need the labels feature.
If it is not the case will it be implemented soon?

Dominant language
Java
Stars
334
Forks
319
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudfoundry/cf-java-client

All issues in cloudfoundry/cf-java-client

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.