b68168807a
backticks, spaces, commas In general, a list of items should have a space after each comma. While there are editorial styles that suggest commas inside quotations, they're horrible advice when the backticks are describing specific character for a user to enter. one off indent filters section singular backticks... word wrap long lines... spelling: macOS contributing: clarify closing case contributing: link to changelog contributing: point to git remote... contributing: split commands from descriptions contributing: grammar spelling: github grammar: comma after etc. spelling: macOS grammar: i.e. alicloud: use relative link alicloud: use backticks alicloud: bits alicloud: such as grammar: comma after etc. avoid linking periods grammar: period amazon-chroot: IOPS amazon-chroot: use backticks amazon-chroot: link to section amazon-chroot: whether-or-not; period amazon-ebs: period amazon-ebs: use relative link amazon-ebs: use backticks amazon-ebs: comma amazon-ebs: bold amazon-ebssurrogate: comma after etc. amazon-ebssurrogate: this builder amazon-instance: this builder amazon-ebssurrogate: set this amazon-ebssurrogate: whether-or-not amazon-ebssurrogate: period amazon-ebssurrogate: bold section reference amazon-ebssurrogate: backticks... amazon-ebssurrogate: commas around e.g. spelling: precedence spelling: i.e. amazon-ebssurrogate: backticks...
17 lines
759 B
Markdown
17 lines
759 B
Markdown
Here's a list of things we like to get done in no particular order:
|
|
|
|
- [ ] Blob/image copy post-processor
|
|
- [ ] Blob/image rename post-processor
|
|
- [ ] SSH to private ip through subnet
|
|
- [ ] chroot builder
|
|
- [ ] support cross-storage account image source (i.e. pre-build blob copy)
|
|
- [ ] look up object id when using device code (graph api /me ?)
|
|
- [ ] device flow support for Windows
|
|
- [x] look up tenant id in all cases (see device flow code)
|
|
- [ ] look up resource group of storage account
|
|
- [ ] include all _data_ disks in artifact too
|
|
- [ ] windows sysprep provisioner (since it seems to generate a certain issue volume)
|
|
- [ ] allow arbitrary json patching for deployment document
|
|
- [ ] tag all resources with user-supplied tag
|
|
- [ ] managed disk support
|