sumanprasad007 / asp-dotnet-app-github-action-pipeline

An Enthusiast Cloud DevOps Engineer from India

• 🔭 I’m currently working as Cloud DevOps Engineer & building CI/CD Pipelines

• TWS Community Builder 🔄 Checkout the Page on LinkedIn

• Completed 90DaysOfDevops Challenge 🚀 Checkout my #90days Journey😊

• My YouTube Channel 🎥 👉 Click here

• 🌱 I’m currently learning AWS CI/CD Pipeline which comprises of CodeCommit, CodeBuild, CodeDeploy, CodePipeline, S3, EC2, Cloudwatch, IAM

• 👯 I’m looking to collaborate on DevOps Project

• 👨‍💻 All of my projects are available at https://github.com/sumanprasad007

• 📝 I regularly write articles on https://sumanprasad.hashnode.dev

• 📫 How to reach me https://linkedin.com/in/prasad-suman-mohan/

• 📄 Know about my experiences https://resume.creddle.io/resume/d4w83xdmskj

• ⚡ Fun fact I'm a Cloud DevOps Engineer, Tech Blogger, Cricketer, Trekker, 10 Fingers-Fast Typist: 60 + WPM, Communicator and Community contributor

Connect with me:

Languages and Tools:

asp-dotnet-app-github-action-pipeline's Issues

Fix code scanning alert - Bad HTML filtering regexp

Tracking issue for:

• https://github.com/sumanprasad007/asp-dotnet-app-github-action-pipeline/security/code-scanning/23

Build .NET Standard application

Description:
The objective of this issue is to build a .NET Standard application specifically for Windows Server using MSBuild, the Microsoft Build Engine. MSBuild is a powerful build platform used for creating applications, libraries, and other software components in the .NET ecosystem.

Problem Statement:
Currently, there is a need to build a .NET Standard application targeting Windows Server using MSBuild. However, there are challenges and uncertainties regarding the correct configuration and steps required to accomplish this task.

Expected Outcome:
By addressing this issue, we aim to provide clear guidance and instructions for successfully building a .NET Standard application for Windows Server using MSBuild. This will enable developers to efficiently compile and package their applications for deployment on Windows Server environments.

Beanstalk Deployment

Description:
This issue focuses on deploying applications or services to the AWS (Amazon Web Services) cloud environment. AWS offers a wide range of services and tools that enable developers to deploy their applications securely, scale them efficiently, and leverage the benefits of cloud computing.

Problem Statement:
There is a need to deploy an application or service to the AWS cloud, but there are challenges and uncertainties surrounding the deployment process. Understanding the various AWS services, configurations, and best practices for deployment can be overwhelming for developers.

Expected Outcome:
By addressing this issue, we aim to provide clear guidance and instructions for successfully deploying applications or services to the AWS cloud. This will empower developers to leverage the power of AWS and efficiently deploy their applications, ensuring scalability, availability, and security.

Tasks:

Research the different deployment options provided by AWS, such as EC2 instances, Elastic Beanstalk, Lambda functions, and containers (using services like ECS or EKS).
Identify the requirements, prerequisites, and configurations necessary for deploying applications or services to the AWS cloud.
Document the step-by-step process of deploying an application to AWS, including the necessary setup and configuration steps.
Provide examples and code snippets demonstrating the deployment process for different types of applications (e.g., web applications, microservices, serverless functions).
Explain how to manage application dependencies, environment variables, and other runtime configurations in the AWS cloud environment.
Address security considerations during deployment, such as IAM roles, access control, encryption, and network configuration.
Discuss monitoring and logging practices to ensure effective management and troubleshooting of deployed applications.
Include recommendations for scalability and availability, covering concepts like auto-scaling, load balancing, and fault tolerance.
Collaborate with the AWS community and refer to official AWS documentation to ensure accuracy and incorporate any updates or best practices.
Test the deployment process on different AWS configurations and validate the results.
Offer troubleshooting tips and solutions for common deployment issues or errors that developers might encounter.
Additional Notes:
Consider the different AWS regions and services available while addressing this issue. Make the documentation comprehensive and accessible to developers with varying levels of experience, from beginners to advanced users.

By addressing this issue, we aim to equip developers with the knowledge and resources needed to confidently deploy their applications or services to the AWS cloud, enabling them to leverage the benefits of AWS infrastructure and services.

Deploy to AWS S3 Bucket - Artifacts

Description:
This issue focuses on deploying applications or services to the AWS (Amazon Web Services) cloud environment. AWS offers a wide range of services and tools that enable developers to deploy their applications securely, scale them efficiently, and leverage the benefits of cloud computing.

Problem Statement:
There is a need to deploy artifacts to the AWS S3 bucket so that it can act as a source for the further deployment stages and also a backup for our publish files.

Upload the artifact to the workflow for post-build stage

Wanted to create artifact out of the build and upload it to the workflow for further deployment stages