Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

ManifestV3 toYaml labels and annotations not correctly mapped

Open
#1,188 0 comments 0 reactions 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
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
cloud

Research direction

Start by locating the ManifestV3 toYaml conversion entry point and the code that maps labels and annotations. Reproduce the generated YAML from the reported manifest and verify that both fields are nested under metadata so Cloud Foundry updates them correctly.

Written by the indexing model from the issue text.

Description

Hello,
When i try to set labels and annotations in the manifestV3 the generated yaml is incorrect:

"env" -> {Collections$UnmodifiableMap@13701}  size = 5
"health-check-http-endpoint" -> "/actuator/health"
"health-check-type" -> "http"
"labels" -> {Collections$UnmodifiableMap@13707}  size = 9
"name" -> "MYAPP"
"path" -> "/tmp/14212678060123353942.jar"
"routes" -> {ArrayList@13713}  size = 2
"services" -> {ArrayList@13715}  size = 3

But the labels and annotations have to be wrapped into a metadata field.
So cloud foundry doesn't update the labels and annotations

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.