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

Add support for Custom Kubernetes Resources #10598

Merged
merged 2 commits into from
May 2, 2023

Conversation

shenglol
Copy link
Contributor

@shenglol shenglol commented May 2, 2023

Updated KubernetesResourceTypeProvider.TryGenerateFallbackType to always return a generic fallback type.

Closes Azure/bicep-extensibility#128.

Microsoft Reviewers: Open in CodeFlow

namespace: 'default'
kubeConfig: ''
}
resource crd 'custom/Foo@v1' = {
Copy link
Member

@anthony-c-martin anthony-c-martin May 2, 2023

Choose a reason for hiding this comment

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

How do we distinguish whether the user intended to use a Kubernetes fallback type vs an ARM fallback type?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@shenglol shenglol merged commit 3f08ffb into main May 2, 2023
@shenglol shenglol deleted the shenglol/k8s-custom-resource-types branch May 2, 2023 20:31
@justinmchase
Copy link

So let me get this right, it still won't generate the custom type but it will generate a fallback type. That will enable bicep to still build successfully you just won't get full intellisense and whatnot?

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.

Unable to create Custom Kubernetes Resources
3 participants