Skip to content

Conversation

tcdowney
Copy link
Member

@tcdowney tcdowney commented Jun 23, 2025

The user field was added in #4407, but this failed for unstaged Docker apps since they do not have JSON-parseable execution metadata.

This fix updates the code to treat empty and unparseable execution metadata the same as an empty JSON object.

  • I have reviewed the contributing guide

  • I have viewed, signed, and submitted the Contributor License Agreement

  • I have made this pull request to the main branch

  • I have run all the unit tests using bundle exec rake

  • I have run CF Acceptance Tests

I ran the Docker subset of CATS that were previously failing. Currently more CATS now.
Update: The ~80 CATS from default CAPI BOSH Lite CATS config passed.

- The user field was added in #4407
- This failed for unstaged Docker apps since they do not have
  JSON-parseable execution metadata
- This fix updates the code to treat empty and unparseable execution
  metadata the same as an empty JSON object
@tcdowney tcdowney merged commit 903f90d into main Jun 23, 2025
18 of 19 checks passed
ari-wg-gitbot added a commit to cloudfoundry/capi-release that referenced this pull request Jun 23, 2025
Changes in cloud_controller_ng:

- Fix GET Process endpoint for unstaged docker apps
    PR: cloudfoundry/cloud_controller_ng#4415
    Author: Tim Downey <[email protected]>
@moleske moleske deleted the fix-docker-no-start branch June 24, 2025 02:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants