azure-quickstart-templates
strictyaml
Our great sponsors
azure-quickstart-templates | strictyaml | |
---|---|---|
42 | 21 | |
13,708 | 1,411 | |
0.9% | - | |
9.9 | 1.9 | |
6 days ago | about 2 months ago | |
Bicep | Python | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
azure-quickstart-templates
- Instantly Deploy BrowserBox on Azure Cloud – open-source isolated browser
- Deploy BrowserBox from an Azure Quickstart Template
- Chef extension for Azure VM
-
Chef extension for Azure VM in Bicep
I found a quick start template for this in Arm, I’m sure if you just decompile the ARM json it will give you a good heads start on how it should work.
-
Bicep: Cyclical Dependency Issue (Network resources)
There is a GitHub issue regarding this topic - https://github.com/Azure/azure-quickstart-templates/issues/2786
- Struggling to understand "_artifactsLocation" parameter when using ARM templates
-
Removing secondary disk
I'm using this video (https://www.youtube.com/watch?v=J4NCvIMuzVE) as a guide to start building out Windows VM's, and running into some questions. I'm trying to use the template located here ( azure-quickstart-templates/quickstarts/microsoft.compute/vm-simple-windows at master · Azure/azure-quickstart-templates (github.com)).
- The yaml document from hell
-
ARM / Bicep template development just by hand?
You can use quick start templates (https://github.com/Azure/azure-quickstart-templates/) as a starting point, but not all examples are bicep ready yet. But those can be easily converted to bicep.
-
SFTP for Azure Blob Storage Generally Available - Pricing
I think it was this one https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.containerinstance/aci-sftp-files-existing-storage and this https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.containerinstance/aci-sftp-files
strictyaml
- StrictYAML
-
XML is better than YAML
NestedText already is the way I use YAML; everything is intepreted as a string. I have some trust in my YAML parser to not mangle most strings. I could use NestedText, but users would be unfamiliar with it, and IIRC the only parsers are in Python. But then I could use StrictYaml too https://github.com/crdoconnor/strictyaml
-
The new type of SQL injection
you can stick to a subset of YAML syntax (e.g. strictYAML)
-
DO YOU YAML?
YAML stands for "YAML Ain’t Markup Language" - this is known as a recursive acronym. YAML is often used for writing configuration files. It’s human readable, easy to understand and can be used with other programming languages. Although YAML is commonly used in many disciplines, it has received criticism on the amoutn of whitespace .yml files have, difficulty in editing, and complexity of the standard. Despite the criticism, properly using YAML ensures that you can reproduce the results of a project and makes sure that the virtual environment packages play nicely with system packages. (If you're looking for another way to share environments there are other alternatives to YAML which include StrictYAML (a type-safe YAML parser) and NestedText)
-
The yaml document from hell
The example you linked provides this as an example of a YAML document that he wants his format to support.
-
The YAML Document from Hell
That safe subset exists and is implemented in a number of languages. It is called strict-yaml: https://hitchdev.com/strictyaml/
-
Hacker News top posts: Jul 3, 2022
StrictYAML\ (33 comments)
-
Why JSON Isn’t a Good Configuration Language (2018)
To me those are in the category of "nice to have", and the problem is that every developer has different preferences for these [1] [2]. But the main features of StrictYaml, like supporting comments and less syntactic noise, I think are pretty uncontroversial, and perhaps it's worth it to get people to switch over for those alone. It doesn't need to be perfect, it just needs to be a significant enough improvement over JSON, and I'd say those two features are more than enough
[1]: https://github.com/crdoconnor/strictyaml/issues/37
[2]: https://github.com/crdoconnor/strictyaml/issues/38
What are some alternatives?
bicep - Bicep is a declarative language for describing and deploying Azure resources
pyyaml - Canonical source repository for PyYAML
photoprism-auto-index - Photoprism supercharged with originals folder auto indexing
nestedtext - Human readable and writable data interchange format
f5-azure-arm-templates - Azure Resource Manager Templates for quickly deploying BIG-IP services in Azure
ytt - YAML templating tool that works on YAML structure instead of text
Enterprise-Scale - The Azure Landing Zones (Enterprise-Scale) architecture provides prescriptive guidance coupled with Azure best practices, and it follows design principles across the critical design areas for organizations to define their Azure architecture
crudini - A utility for manipulating ini files
protonmail-bridge-docker - ProtonMail IMAP/SMTP Bridge Docker container
yaml-rust - A pure rust YAML implementation.
opnazure - This template allows you to deploy an OPNsense Firewall Azure VM using the opnsense-bootsrtap installation method
starlark-go - Starlark in Go: the Starlark configuration language, implemented in Go