Console UI strips custom provider attribute values (e.g., `testissue`) from `MsgCreateDeployment` TX

Open
#1,133 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
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
blockchain, frontend

Research direction

Start at the Console's Deploy → Upload your SDL flow and trace how the SDL becomes the MsgCreateDeployment transaction. Compare the custom testissue attribute with the provider-services CLI output; done means the submitted transaction preserves its value as 300.

Written by the indexing model from the issue text.

Description

When deploying via the Akash Console, the MsgCreateDeployment transaction omits or strips certain custom provider attribute values defined in the SDL.

Steps to Reproduce:
  1. Navigate to: Deploy -> Upload your SDL
  2. Upload the following SDL (Load it from file stored on your local disk):
---
version: "2.0"

services:
  tetris:
    image: bsord/tetris
    expose:
      - port: 80
        as: 80
        to:
          - global: true
      # SSH port
      - port: 22
        as: 22
        to:
          - global: true

profiles:
  compute:
    tetris:
      resources:
        cpu:
          units: 2.0
        memory:
          size: 2Gi
        storage:
          - size: 2Gi
  placement:
    akash:
      attributes:
        host: akash
        testissue: 300
      #  datacenter: us-midwest-qci-1
      #  #organization: overclock
      pricing:
        tetris:
          denom: uakt
          amount: 1000000

deployment:
  tetris:
    akash:
      profile: tetris
      count: 1

  1. Confirm that the SDL is correctly displayed in the UI:
    Console UI Preview

  2. Complete the deployment and inspect the resulting transaction.

Expected Result (Using CLI):

When deployed using provider-services CLI v0.6.10, the attribute is preserved as expected:

$ provider-services query tx EC626B3980964D4341B23C7DFED5AD84A76F60B38FDB6C44390F3A035935F63E | grep -B3 -A1  'key: testissue'
          attributes:
          - key: host
            value: akash
          - key: testissue
            value: "300"
Actual Result (Using Console):

When deploying the same SDL through the Console, the attribute is present but the value is stripped:

$ provider-services query tx BB003122B3CC290E339E2FF1CB91C0084E9EB42EEDD9A2961A791B2B0B3C038A | grep -B3 -A1  'key: testissue'
          attributes:
          - key: host
            value: akash
          - key: testissue
            value: ""
Conclusion:

The Console UI appears to be incorrectly handling custom provider attributes — specifically removing or failing to retain their values when preparing the deployment transaction. This results in unexpected behavior and inconsistency with CLI-based deployments.

Dominant language
TypeScript
Stars
264
Forks
94
Avg merge
18h 49m
Merged PRs (30d)
297

Contributor guide

Open the contributing guide

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 akash-network/console

All issues in akash-network/console

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.