Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/aws-cloudformation/cloudformation-coverage-roadmap
The AWS CloudFormation Public Coverage Roadmap
https://github.com/aws-cloudformation/cloudformation-coverage-roadmap
aws aws-cloudformation cfn cloudformation roadmap
Last synced: 20 days ago
JSON representation
The AWS CloudFormation Public Coverage Roadmap
- Host: GitHub
- URL: https://github.com/aws-cloudformation/cloudformation-coverage-roadmap
- Owner: aws-cloudformation
- License: cc-by-sa-4.0
- Created: 2019-07-24T17:13:55.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2024-04-15T16:51:14.000Z (7 months ago)
- Last Synced: 2024-10-10T17:03:54.606Z (24 days ago)
- Topics: aws, aws-cloudformation, cfn, cloudformation, roadmap
- Homepage: https://aws.amazon.com/cloudformation/
- Size: 51.8 KB
- Stars: 1,105
- Watchers: 155
- Forks: 54
- Open Issues: 1,045
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
## CloudFormation Public Coverage Roadmap
The AWS CloudFormation Public Coverage Roadmap
## Introduction
This is a public roadmap focused on upcoming coverage support for CloudFormation. It is focused on coverage additions to existing AWS services to be addressed by upcoming CloudFormation releases. It represents a preview of the information we provide in our existing release history documentation. Knowing about our upcoming coverage additions and priorities helps our customers plan, and we want to provide a way for our customers to help us ensure we are working on the most important requests.
[See the roadmap »](https://github.com/aws-cloudformation/aws-cloudformation-coverage-roadmap/projects/1)
## Security disclosures
If you think you’ve found a potential security issue, please do not post it in the Issues. Instead, please follow the instructions [here](https://aws.amazon.com/security/vulnerability-reporting/) or [email AWS security directly](mailto:[email protected]).
## FAQs
**Q: Why did you build this?**
A: We know that our customers are making decisions and plans based on what we are developing, and we want to provide our customers the insights they need to plan. If our customers know that a coverage item is being worked on and will be released soon, we can help them avoid additional work if they are considering workarounds or custom resources to address their needs. Further, we want you to help us ensure we are working on the most important and impactful issues.
**Q: Why are there no dates on your roadmap?**
A: Because our main priority is security and operational stability, we cannot provide specific target dates for releases.
**Q: What do the roadmap categories mean?**
* *Shipped* - currently usable in CloudFormation templates
* *Coming soon* - nearing completion, likely being planned for an upcoming coverage update release. Think a couple of weeks out, give or take.
* *We're working on it* - in progress, but further out. We might still be working through the implementation details, or scoping stuff out.
* *Researching* - We're thinking about it. This might mean we're still evaluating designs and options, or thinking through how this should work. This is a great phase to give us feedback as to how you want to see something implemented! We’ll benefit from your specific use cases here.**Q: Is everything on the roadmap?**
A: We are focusing on coverage updates for existing CloudFormation resource types, as well as new and previously available AWS services where there’s no native CloudFormation support yet. There is other coverage-related work that we won’t be able to preview. For example, services that are not publicly released yet will not appear on this roadmap. Finally, there are other non-coverage-related feature work that we won’t cover in this roadmap at this time.
**Q: How can I provide feedback or ask for more information?**
A: When in doubt, please create an issue! Although we’ll focus on coverage issues, all submitted issues will get reviewed and/or forwarded appropriately.
**Q: How can I request a feature be added to the roadmap?**
A: We encourage you to open an issue, even if you’ve requested it before via other channels. All community-submitted issues will be reviewed by the roadmap maintainers. We’ve created a template to make it easy to open new issues.
**Q: Can I "+1" existing issues?**
A: We strongly encourage you to vote on issues, as it helps us understand which issues will have the widest impact, but please don't leave comments saying "+1". Such comments generate noise for people receiving notifications, and issues can't be sorted by number of "+1" comments. Instead, leave a 👍 reaction, which is less noisy and can be used to sort issues for prioritization. To leave a reaction, navigate to the issue details page and add a reaction with the 😀 button on the post. There are six types of reactions supported (thumbs down "-1", confused, heart, watching, laugh, hooray, and thumbs up +1). We can typically do 8-10 items per month with all necessary regression testing, and we want you to help us decide which items will benefit you the most.
## Community
Join us on Discord! Connect & interact with CloudFormation developers &
experts, find channels to discuss and get help for cfn-lint, CloudFormation registry, StackSets,
Guard and more:[![Join our Discord](https://discordapp.com/api/guilds/981586120448020580/widget.png?style=banner3)](https://discord.gg/9zpd7TTRwq)
## License Summary
This project is made available under the CC-BY-SA-4.0 license. See the LICENSE file.
To learn more about the service, go here: http://aws.amazon.com/cloudformation