radius-project / radius-project/radius

Rad resource list is inconsistently case sensitive

Open
#9,799 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug triaged
Dominant language
Go
Stars
1.7k
Forks
137
Avg merge
2d 17h
Merged PRs (30d)
110

Description

Steps to reproduce
  1. Deploy a radius application that contains an Applications.Core/container resource.
  2. Make sure you are in the group and environment containing the application.
  3. Run rad resource list Applications.core/containers, intentionally mis-casing Core.
Observed behavior

Running rad resource list with properly cased resource name returns the resource as expected.

$ rad resource list Applications.Core/containers
RESOURCE       TYPE                          GROUP          STATE
todocontainer  Applications.Core/containers  orchard-group  Succeeded

Running rad resource list with incorrect casing returns an error message indicating that it is case insensitive, however, the results are case sensitive. (The c in Containers is lower case, but the error message indicates it has found the resource even though it returns an error.)

$ rad resource list Applications.core/containers
Resource type "containers" not found in resource provider "Applications.Core".
Desired behavior

rad resource list should either be case sensitive or case insensitive. For usability I suggest it should be insensitive to case.

Results for the command should look like this:

$ rad resource list Applications.core/containers
RESOURCE       TYPE                          GROUP          STATE
todocontainer  Applications.Core/containers  orchard-group  Succeeded
Workaround

No response

rad Version
$ rad version
CLI Version Information:
RELEASE   VERSION   BICEP     COMMIT
0.47.0    v0.47.0   0.36.1    8b18539f5b221e10818d334c68b6763b460267c5

Control Plane Information:
STATUS     VERSION
Installed  0.47.0
Operating system

Ubuntu Linux

Additional context

No response

Would you like to support us?
  • Yes, I would like to support you

AB#16176

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.

Research direction

Start by reproducing the issue with rad resource list Applications.core/containers and compare it with the correctly cased command. Trace the rad resource list command's resource-type lookup and add or update coverage for mixed-case provider and resource names. Done means the command consistently follows the chosen case-sensitivity behavior and returns the expected resource.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.