DefangLabs / DefangLabs/defang-docs
Add per-providers docs on x-defang-policies
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6
- Forks
- 7
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 16
Description
We've added x-defang-policies support to AWS, Azure, and GCP, but this was not documented. Needs clear examples of what the accepted values are for each cloud, and how to use ${…} to move literals out of the Compose file (to keep Compose agnostic) and to .env or .env.<stack> or .env.<provider> files.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing x-defang-policies documentation and provider-specific examples in the Defang docs. Add clear AWS, Azure, and GCP accepted-value examples, plus guidance for using ${…} with .env, .env., and .env. files; done means users can keep Compose provider-agnostic and understand each provider's values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, azure, docker-compose, gcp
- Domain
- cloud, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 76/100