doctl apps spec get not returning authority correctly

[stigrune]

Describe the Issue:
I'm using doctl apps spec get <id> --format json > spec.json

I'm observing that the authority in the response is {}

  "ingress": {
    "rules": [
      {
        "match": {
          "path": {
            "prefix": "/"
          },
          "authority": {}
        },
        "component": {
          "name": "pixelate"
        }
      }
    ]
  },

But in the DigitalOcean Web UI there is an authority added on the app.

I would expect the doctl apps spec get command to return the same values that are
displayed in the web UI.

Environment:

• doctl version: 1.146.0-release
• OS: Tested both Windows 11 and ubuntu-latest via github actions.
• Installation method: winget, and uses: digitalocean/action-doctl@v2

Additional Details:
Also tested yaml with same results, the authority is not set in the spec.

This is a new app created by the Web UI, with deployment source “Container image”, pointing to a DigitalOcean Container Registry image. No manual changes have been done to the spec file.

[anup-deka]

Thanks for raising this issue @stigrune

[Oghenesuvwe-dev]

The issue is that the code is using sigs.k8s.io/yaml library.
This library has known issues with certain struct field serialization, particularly with omitempty tags and pointer fields.

The fix passed 3 checks waiting for a review and possible merge

[SzymonDukla]

The issue is still there, it's been 4 months guys... This prevents spec get -> spec update -> app update workflows from working correctly, effectively halting any automated deployment (and we don't want to manage secrets and local app spec locally)

[aupadhyay-shark]

Bug fix is released -
#1839