second commit

.github/FUNDING.yml

@@ -0,0 +1,3 @@
+# These are supported funding model platforms
+
+github: [codenteq]

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,40 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+---
+name: "🐛 Bug Report"
+about: 'Report a general issue.'
+---
+
+# Bug Report
+<!--- Before you open an issue, please check if the issue already has been reported. --->
+
+## Issue Description
+<!--- Provide a more detailed introduction to the issue itself. -->
+
+## Preconditions
+<!--- Please provide as detailed information about your environment as possible. -->
+
+## Steps To Reproduce
+<!--- It is important to provide a set of clear steps to reproduce this bug. If relevant please include code samples. -->
+
+## Actual Result
+<!--- Tell us what happens instead.-->
+
+## Expected Result
+<!--- Tell us what should happen. -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,22 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+---
+name: "💡 Feature Request"
+about: 'Share your ideas with our team or request new features'
+---

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,12 @@
+## Issue Reference
+<!--- Please mention issue #id or use a comma if your pull request solves multiple issues. -->
+
+## Description
+<!--- Please describe your changes in detail. -->
+
+## How To Test This?
+<!--- Please describe in detail how to test the changes made in this pull request. -->
+
+## Documentation
+- [ ] My pull request requires an update on the documentation repository.
+<!--- Please describe in detail what needs to be changed. --->

.gitignore

@@ -0,0 +1,2 @@
+.idea
+vendor

CHANGELOG.md

@@ -0,0 +1,8 @@
+CHANGELOG
+=========
+
+0.3.0
+---
+
+ * Change to Symfony Azure Bridge
+ * New entry in config and .env file: "resource_name" and "AZURE_MAIL_RESOURCE_NAME"

CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+info@arsivpro.com.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

CONTRIBUTING.md

@@ -0,0 +1,23 @@
+# Azure Mailer Driver Contribution Guide
+
+**BUGS:**
+
+To encourage active collaboration, eCommerce Blog Extension project encourages pull requests, not just bug reports. "Bug reports" may also be sent in the form of a pull request containing a negative test.
+
+However, when filing a bug report, your issue should contain a title and a clear description of the issue. You should also include as much relevant information as possible and a code sample that demonstrates the issue. The goal of a bug report is to make it easy for yourself - and others - to replicate the bug and develop a fix.
+
+Remember, bug reports are created in the hope that others with the same problem will collaborate with you on solving it. Creating a bug report serves to help yourself and others start on the path of fixing the problem.
+
+**Core development ideas or discussion:**
+
+If you propose a new feature, please implement at least some of the code needed to complete the quality.
+
+Informal discussion regarding bugs, new features, and implementation of existing features occurs in the comments of the issues filed using feature template.
+
+**Which branch you should target?**
+
+All bug fixes should be sent to the latest staging branch, i.e. development branch. Bug fixes should never be sent to the master branch unless they fix features that exist only in the upcoming release.
+
+Minor features fully backwards compatible with the current Arduino release may be sent to the latest stable branch.
+
+Major new features should always be sent to the master branch, which contains the upcoming eCommerce Blog Extension release.

LICENSE

@@ -18,4 +18,4 @@ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
 AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+SOFTWARE.

README.md

@@ -1,2 +1,78 @@
-# azure-mailer-driver
-The Microsoft Azure ACS integration for Symfony Mailer.
+# Microsoft Azure Mailer Driver
+
+[![Latest Stable Version](http://poser.pugx.org/codenteq/azure-mailer-driver/v)](https://packagist.org/packages/codenteq/azure-mailer-driver)
+[![Total Downloads](http://poser.pugx.org/codenteq/azure-mailer-driver/downloads)](https://packagist.org/packages/codenteq/azure-mailer-driver)
+[![License](http://poser.pugx.org/codenteq/azure-mailer-driver/license)](https://github.com/codenteq/azure-mailer-driver/blob/master/LICENSE)
+
+## 1. Introduction:
+
+The integration of Microsoft Azure ACS for Symfony Mailer provides a simple and clean email API supported by the [Symfony Azure Mailer Bridge](https://github.com/symfony/azure-mailer) component.
+
+## 2. Requirements
+
+* **PHP**: 8.1 or higher.
+* **Composer**: 1.6.5 or higher.
+
+## 3. Installation
+
+First time using Azure ECS? Create your [Azure account](https://azure.com), if you don’t have one already.
+
+- Run the following command
+```bash
+composer require codenteq/azure-mailer-driver
+```
+
+### Set mail config
+
+> WARNING <br>
+> It will check existence of the `config/mail.php` file, if it exists then please update the file manually with the below details.
+
+```php
+'mailers' => [
+        'azure' => [
+            'transport'             => 'azure',
+            'resource_name'         => env('AZURE_MAIL_RESOURCE_NAME'),
+            'endpoint'              => env('AZURE_MAIL_ENDPOINT', 'https://my-acs-resource-name.communication.azure.com'),
+            'access_key'            => env('AZURE_MAIL_KEY'),
+            'api_version'           => env('AZURE_MAIL_API_VERSION', '2023-03-31'),
+            'disable_user_tracking' => env('AZURE_MAIL_DISABLE_TRACKING', false),
+            'client' => [
+                'max_host_connections' => 10,
+                'max_pending_pushes' => 100,
+            ]
+        ],
+```
+
+> WARNING <br>
+> It will check existence of the .env file, if it exists then please update the file manually with the below details.  
+
+```bash 
+  # Mail service entries... 
+  MAIL_MAILER=azure
+
+  # Azure Service entries
+  AZURE_MAIL_RESOURCE_NAME=my-acs-resource-name
+  # AZURE_MAIL_ENDPOINT= #optional
+  AZURE_MAIL_KEY=Base64AzureAccessToken
+  # AZURE_MAIL_API_VERSION=2023-03-31 #optional
+  # AZURE_MAIL_DISABLE_TRACKING=false #optional
+
+```
+
+> just sent your notification mail messages!
+
+## Available resources
+
+| Resource             | Status   |
+| -------------------- | :------: |
+| Plain Text           | ✅  |
+| HTML                 | ✅  |
+| Attachments          | ✅  |
+| Multiple recipients  | ✅  |
+| Auth HMAC-SHA256     | ✅  |
+| Notifications        | ✅  |
+| Mkt Campaigns        | ✅  |
+| Markdown             | ✅  |
+
+## How to contribute
+Azure Mailer Driver is always open for direct contributions. Contributions can be in the form of design suggestions, documentation improvements, new component suggestions, code improvements, adding new features or fixing problems. For more information please check our [Contribution Guideline document.](https://github.com/codenteq/azure-mailer-driver/blob/master/CONTRIBUTING.md)

RELEASE.md

@@ -0,0 +1,3 @@
+# Release Instructions
+
+[Releases](https://github.com/codenteq/azure-mailer-driver/releases) are done by [@codenteq](https://github.com/codenteq) for this repository.

SECURITY.md

@@ -0,0 +1,21 @@
+# Security Policy
+
+## Supported Versions
+
+Use this section to tell people about which versions of your project are
+currently being supported with security updates.
+
+| Version | Supported          |
+| ------- | ------------------ |
+| 5.1.x   | :white_check_mark: |
+| 5.0.x   | :x:                |
+| 4.0.x   | :white_check_mark: |
+| < 4.0   | :x:                |
+
+## Reporting a Vulnerability
+
+Use this section to tell people how to report a vulnerability.
+
+Tell them where to go, how often they can expect to get an update on a
+reported vulnerability, what to expect if the vulnerability is accepted or
+declined, etc.