- Notifications
You must be signed in to change notification settings - Fork22
Open
Labels
Description
Agent metadata currently does not support ordering in the same way users can orderapps oragents. We should use the existing syntax to allow ordering metadata items on any resource. Each resource should have an independent index.
Agent metadata ordering
The existing implementation:
resource"coder_agent""dev" {os="linux"...metadata {display_name="CPU Usage"key="cpu_usage"script="coder stat cpu"interval=10timeout=1order=2 }metadata {display_name="RAM Usage"key="ram_usage"script="coder stat mem"interval=10timeout=1order=1 }order=1}
Resource Metadata ordering
Proposal:
resource"coder_metadata""pod_info" {count=data.coder_workspace.me.start_countresource_id=kubernetes_pod.dev[0].id# (Enterprise-only) this resource consumes 200 quota unitsdaily_cost=200item {key="pod_uid"value=kubernetes_pod.dev[0].uidorder=2# new! }item {key="description"value="This description will show up in the Coder dashboard."order=1# new! }item {key="public_key"value=tls_private_key.example_key_pair.public_key_opensshorder=3# new! }}