Metadata manifest attribute not supported
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 50/100
Research direction
Begin at ApplicationManifestUtilsV3.read and write, using the provided manifest and output as the reproduction. Trace how metadata is represented during that round trip, preserve the labels and annotations described in the issue, and verify that the resulting manifest retains them.
Written by the indexing model from the issue text.
Description
The cloud foundry app manifest supports a metadata attribute for setting labels and annotations: https://docs.cloudfoundry.org/devguide/deploy-apps/manifest-attributes.html#metadata
However, this attribute seems to be ignored by the cf-java-client.
How to reproduce
Here is a minimal example that reproduces the issue:
ManifestV3 manifest = ApplicationManifestUtilsV3.read(Path.of("test-manifest-with-labels.yaml"));
ApplicationManifestUtilsV3.write(Path.of("test-manifest-result.yaml"), manifest);
Content of test-manifest-with-labels.yaml:
---
applications:
- name: test-app
memory: 1G
instances: 1
metadata:
labels:
test-label: "test-value"
Content of test-manifest-result.yaml after the snippet above has run:
---
applications:
- name: test-app
memory: 1G
instances: 1
As you can see, the metadata information has been removed. When using the cf-java-client to deploy such a manifest, the metadata labels and annotations are therefore discarded. I would expect the attributes mentioned in the cloud foundry documentation to be supported by this client library, including the metadata attribute.
- Dominant language
- Java
- Stars
- 334
- Forks
- 319
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cloudfoundry/cf-java-client
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
cloudfoundry/cf-java-client#1374 ·
-
Integration tests fail: test-service-broker.jar incompatible with java-buildpack v5 (JDK 17 default) Open
Difficulty 2/5 Half a day Newbie friendliness 74/100
cloudfoundry/cf-java-client#1344 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
cloudfoundry/cf-java-client#1373 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
cloudfoundry/cf-java-client#1370 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
cloudfoundry/cf-java-client#1367 ·
All issues in cloudfoundry/cf-java-client
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
elastic/gradle-plugins#157 ·
-
enhancement Tools
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
apache/rocketmq-dashboard#5008 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
DETECT_PARAMETER_NAMES=false silently disables @ConstructorProperties-based Creator detection too Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FasterXML/jackson-databind#6229 ·