Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/snyk/driftctl-orb

CircleCI driftctl orb
https://github.com/snyk/driftctl-orb

driftctl infrastructure-as-code

Last synced: 3 months ago
JSON representation

CircleCI driftctl orb

Awesome Lists containing this project

README

        

# driftctl Orb for CircleCI

[![CircleCI Build Status](https://circleci.com/gh/snyk/driftctl-orb.svg?style=shield "CircleCI Build Status")](https://circleci.com/gh/snyk/driftctl-orb) [![CircleCI Orb Version](https://badges.circleci.com/orbs/snyk/driftctl.svg)](https://circleci.com/orbs/registry/orb/snyk/driftctl) [![GitHub License](https://img.shields.io/badge/license-MIT-lightgrey.svg)](https://raw.githubusercontent.com/snyk/driftctl-orb/master/LICENSE) [![CircleCI Community](https://img.shields.io/badge/community-CircleCI%20Discuss-343434.svg)](https://discuss.circleci.com/c/ecosystem/orbs)

Scan your infrastructure with the official driftctl Orb. Detect, track and alert on infrastructure drift.

---

## Resources

[CircleCI Orb Registry Page](https://circleci.com/orbs/registry/orb/snyk/driftctl) - The official registry page of this orb for all versions, executors, commands, and jobs described.

[CircleCI Orb Docs](https://circleci.com/docs/2.0/orb-intro/#section=configuration) - Docs for using, creating, and publishing CircleCI Orbs.

---

### How to Contribute

We welcome [issues](https://github.com/snyk/driftctl-orb/issues) to and [pull requests](https://github.com/snyk/driftctl-orb/pulls) against this repository!

### How to Publish An Update
1. Merge pull requests with desired changes to the main branch.
- For the best experience, squash-and-merge and use [Conventional Commit Messages](https://conventionalcommits.org/).
2. Find the current version of the orb.
- You can run `circleci orb info snyk/driftctl | grep "Latest"` to see the current version.
3. Create a [new Release](https://github.com/snyk/driftctl-orb/releases/new) on GitHub.
- Click "Choose a tag" and _create_ a new [semantically versioned](http://semver.org/) tag. (ex: v1.0.0)
- We will have an opportunity to change this before we publish if needed after the next step.
4. Click _"+ Auto-generate release notes"_.
- This will create a summary of all of the merged pull requests since the previous release.
- If you have used _[Conventional Commit Messages](https://conventionalcommits.org/)_ it will be easy to determine what types of changes were made, allowing you to ensure the correct version tag is being published.
5. Now ensure the version tag selected is semantically accurate based on the changes included.
6. Click _"Publish Release"_.
- This will push a new tag and trigger your publishing pipeline on CircleCI.