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

Small readme tweaks, removed a known limitation #2778

Merged
merged 3 commits into from
May 24, 2021

Conversation

alex-frankel
Copy link
Collaborator

Fixes #2754

Contributing to documentation

  • The contribution does not exist in any of the docs in either the root of the docs directory or the specs

README.md Outdated
@@ -7,7 +7,8 @@

## What is Bicep?

Bicep is a Domain Specific Language (DSL) for deploying Azure resources declaratively. It aims to drastically simplify the authoring experience with a cleaner syntax, improved type safety, and better support for modularity and code re-use. Bicep is a **transparent abstraction** over ARM and ARM templates, which means anything that can be done in an ARM Template can be done in Bicep (outside of temporary [known limitations](#known-limitations)). All resource `types`, `apiVersions`, and `properties` that are valid in an ARM template are equally valid in Bicep on day one.
Bicep is a Domain Specific Language (DSL) for deploying Azure resources declaratively. It aims to drastically simplify the authoring experience with a cleaner syntax, improved type safety, and better support for modularity and code re-use. Bicep is a **transparent abstraction** over ARM and ARM templates, which means anything that can be done in an ARM Template can be done in Bicep (outside of temporary [known limitations](#known-limitations)). All resource `types`, `apiVersions`, and `properties` that are valid in an ARM template are equally valid in Bicep on day one (Note: it is possible that type information for a resource may be missing, but it is still deployable).
Copy link
Member

Choose a reason for hiding this comment

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

[nit] This reads a bit to me like "it is possible that the resource may still be deployable", whereas it should read more clearly as "your resource will always be deployable despite type availability"

What about something like Note: even if Bicep type information is not available for a resource, it can still be deployed

@alex-frankel alex-frankel merged commit 82ec9dc into main May 24, 2021
@alex-frankel alex-frankel deleted the alex-frankel-patch-2 branch May 24, 2021 23:23
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.

Latest API versions not available
2 participants