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

Conversation

vishwahiremat
Copy link
Contributor

Today if there is a typo is radius resource types, it throws an error 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/ adding it in the docs .

Copy link
Contributor

@kachawla kachawla left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vishwahiremat a couple of comments. Let's also get a PM review on this. Thanks.

@@ -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 will result in an 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:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Deploying a Radius Resources with a typo in the resource type will result in an 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:
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/
```

As a workaround make sure to use correct resource type names while defining radius resources.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
As a workaround make sure to use correct resource type names while defining radius resources.
We are working on making this error clearer. In the meantime, when you see this error please make sure to ensure that the resource type name is correctly specified while defining radius resources in your application/environment bicep file.

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 make sure to ensure that the resource type name is correctly specified while defining radius resources in your application/environment bicep file.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
We are working on making this error clearer. In the meantime, when you see this error please make sure to ensure that the resource type name is correctly specified while defining radius resources in your application/environment bicep file.
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.

Signed-off-by: Vishwanath Hiremath <[email protected]>
This reverts commit a8f22c5.

Signed-off-by: Vishwanath Hiremath <[email protected]>
Signed-off-by: Vishwanath Hiremath <[email protected]>
Signed-off-by: Vishwanath Hiremath <[email protected]>
Signed-off-by: Vishwanath Hiremath <[email protected]>
@vishwahiremat vishwahiremat force-pushed the vishwahiremat/addingResourceTypoLimitation branch from 9cf1bfd to c7a1508 Compare March 18, 2025 20:55
@willtsai willtsai merged commit 1d36811 into radius-project:edge Mar 19, 2025
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants