aws-samples / aws-samples/aws-net-guides
Update step-by-step guide "Create a deployment pipeline between VSTS and AWS Elastic Beanstalk"
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 255
- Forks
- 97
- PR merge metrics
- No merged PRs in 30d
Description
Needs updates for product names and screenshots.
- Use of "VSTS" should be replaced with Azure DevOps, including in our own product names
- Screenshots of marketplaces, etc, should be refreshed.
- When creating application in Beanstalk, set context that the Azure DevOps task expects the app and environment to exist (currently not mentioned)
- Update new project workflow to generate an ASP.NET Core 5 project (currently 2.x)
- Use Linux-based EB environment (currently Windows)
- Remove advertorial sections on Visual Studio toolkit; not relevant to this guide
Guide folder: Deployment/ASP.Net_Core_to_ElasticBeanstalk_from_VSTS
Contributor guide
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 in _Deployment/ASP.Net_Core_to_ElasticBeanstalk_from_VSTS/ and review the guide for outdated product names, screenshots, project workflow, environment choice, and advertorial sections. Done means the guide reflects Azure DevOps, current marketplace imagery, an existing Elastic Beanstalk application and environment, an ASP.NET Core 5 project, a Linux environment, and no irrelevant toolkit advertising.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, azure
- Domain
- cloud, devops, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100