Skip to main content

Stack Resources tab should show address instead of name

Feature RequestsResourcesUI/UX

Since names can be repeated (like “this”), displaying the full address will help to identify the resource/output/whatever in the list.

Currently, you can find yourself checking entry by entry until finding the proper resource by looking to the address, which is a time consuming task.

Status: ✅ Completed6 comments

Log in to comment and vote

Comments6

  • Black Breeze

    •

    Jun 9, 2025

    We've reviewed this feedback and agree this is a clear UX inefficiency worth fixing. We're planning to address: 1. **Make Name column optional** - Allow hiding/moving the Name field like any other column 2. **Enable arbitrary column resizing** - Let users resize columns as needed, even with horizontal scrollbar 3. **Remove default stack grouping** - When in stack view, default to no grouping since "Group by Stack" is redundant The goal is to make resource identification much faster by prioritizing the full address over the less-useful name field. Thanks for the detailed feedback and examples!

  • Black Breeze

    •

    Jun 9, 2025

    The new resources view allows you to make the address more prominent but indeed does not allow you to hide or move the “Name” column. Is this acceptable?

    If no, then the next quickest option for us would be to you rather have us give you the ability to hide the “Name” column, and potentially resize the Resource address column to fit most resource names. What do you reckon?

  • Brown Meteorite

    •

    Apr 30, 2025

    When it comes to Tofu/Terraform we would also benefit from this.

    For me it feels like the most useful view is the stack view (“Stack > Resources”), but it seems like if “Resources” view was designed first and copied into the stack level view. And feels like this is not optimized for the 99% of the cases where you only have 1 single stack, however the default “Grouped by” is “Stack”, and the colums “Resources”, “Space” and “Vendor” have no sense here and are wasting column space.

    When it comes to the name of the resource, it’s very confusing as well: For Tofu/Terraform, imagine you have a stack with a simple resource “module.this.aws_iam_role.this”. The stack’s resources view only gives you “this”, as an identifier, which makes you waste time having to click to the resource and read the JSON to see whether it’s the resource you are looking for. Yes, you can group by provider (and have “aws_iam_role.this“), but you are still missing the module info.

    Also, performing a resource lookup in the search bar doesn’t match the full address.

    For me it feels like the default view should allow you to see the full address (“module.this.aws_iam_role.this”), and the default “Group by“ should be “none”, as it lacks sense at stack level (btw, grouping by module also makes sense, but not as the default option).

    For stacks using Terragrunt or Ansible probably the resource view should be slightly different, but in any case, the stack resources view can definitely be optimized in order to grant a usable QoL to users.

  • Aquamarine Savanna

    •

    Apr 30, 2025

    Also, since the stacks don’t necessarily need to be terraform, maybe it could make sense to have a label to identify the resource kind. At the end, at least for Terraform, the Resources list would be way more useful if it’s like the terraform state list, having a list of addresses. For other cases I can’t tell.