lowlydba / lowlydba.sqlserver

:spoon: A cross-platform Ansible collection using PowerShell to configure and maintain SQL Server.

lowlydba.sqlserver Collection for Ansible

• Modules
• Code of Conduct
• Communication
• Contributing to this collection
• Collection maintenance
• Tested with
  • Ansible
  • SQL Server
• External requirements
• Using this collection
  • Installing the Collection from Ansible Galaxy
• Releasing
  • Release notes
  • Next Release
  • Schedule
  • Versioning
  • Deprecation

Modules

For the most up to date information, see the plugin section of the documentation for this collection (https://lowlydba.github.io/lowlydba.sqlserver).

For the current version contained in the Ansible Community General Collection, see the official documentation.

Code of Conduct

We follow the Ansible Code of Conduct in all our interactions within this project.

If you encounter abusive behavior, please refer to the policy violations section of the Code for information on how to raise a complaint.

Communication

Join us in the #ansible (general use questions and support), #ansible-community (community and collection development questions), and other IRC channels.

We take part in the global quarterly Ansible Contributor Summit virtually or in-person. Track The Bullhorn newsletter and join us.

For more information about communication, refer to the Ansible Communication guide.

Contributing to this collection

The content of this collection is made by people like you, a community of individuals collaborating on making the world better through developing automation software. We are actively accepting new contributors.

We use the following guidelines:

• CONTRIBUTING.md
• REVIEW_CHECKLIST.md
• Ansible Community Guide
• Ansible Development Guide
• Ansible Collection Development Guide

Collection maintenance

The current maintainers are listed in the MAINTAINERS file. If you have questions or need help, feel free to mention them in the proposals.

To learn how to maintain / become a maintainer of this collection, refer to the Maintainer guidelines.

Tested with

Ansible

• 2.13
• 2.14
• 2.15
• dlevel

SQL Server

• SQL Server 2000 - current (via DBATools)
• Azure SQL Database Managed Instance - YMMV

External requirements

• PowerShell modules
  • dbatools >= 2.0.0
  • dbops >= 0.9.0

Using this collection

Installing the Collection from Ansible Galaxy

Before using this collection, you need to install it with the Ansible Galaxy command-line tool:

ansible-galaxy collection install lowlydba.sqlserver

You can also include it in a requirements.yml file and install it with ansible-galaxy collection install -r requirements.yml, using the format:

---
collections:
  - name: lowlydba.sqlserver

Note that if you install the collection from Ansible Galaxy, it will not be upgraded automatically when you upgrade the ansible package. To upgrade the collection to the latest available version, run the following command:

ansible-galaxy collection install lowlydba.sqlserver --upgrade

You can also install a specific version of the collection, for example, if you need to downgrade when something is broken in the latest version (please report an issue in this repository). Use the following syntax to install version 0.1.0:

ansible-galaxy collection install lowlydba.sqlserver:==0.1.0

See Ansible Using collections for more details.

Releasing

Release notes

See the changelog.

Next Release

No major release planned currently.

Schedule

• Minor releases and patches will aim to be released within 2 weeks of being merged into main or when necessary.
• Non-current minor versions will not generally be patched, since there is little expected breaking of backwards compatibility.
  • If this does occur, an exception can be made.

Versioning

This project adheres to semantic versioning as tracked in galaxy.yml.

Deprecation

• Deprecations are done by version number (not by date).
• New deprecations can be added during every minor release, under the condition that they do not break backwards compatibility.
• Deprecations are expected to have a deprecation cycle of at least 2 major versions (i.e. ~1 year). Maintainers can use a longer deprecation cycle if they want to support the old code for that long.