Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding a new limitation to call out typos in radius resource type #1405

Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion .github/config/en-custom.txt
Original file line number Diff line number Diff line change
Expand Up @@ -1296,4 +1296,5 @@ DaprConfigurationStoreProperties
configurationStores
configurationstores
Oras
oras
oras
DeploymentTemplate
8 changes: 8 additions & 0 deletions docs/content/reference/limitations.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,14 @@ Error - Type: IncludeError, Status: True, Reason: RootIncludesRoot, Message: roo

As a workaround make sure to use distinct names for both containers and gateways.

### Typos in Radius Resource Type Names
Deploying a Radius Resources with a typo in the resource type or an unsupported resource type will result in an Azure provider related error being thrown during deployment. For example, when `Application.Core/Extenders` is defined as `Application.Core/Extender` you will get an error messaging similar to:
```
Azure deployment failed, please ensure you have configured an Azure provider with your Radius environment: https://docs.radapp.io/guides/operations/providers/azure-provider/
```

We are working on making this error clearer. In the meantime, when you see this error please ensure that the resource type name is correctly specified in your Radius Application or Environment Bicep file.

## rad CLI

### Application and resource names are lower-cased after deployment
Expand Down
Loading