Giter VIP home page Giter VIP logo

nr-ansible's Introduction

Contributors Issues License Lifecycle:Experimental

Testing

Create a Scenario

molecule init scenario fluent_bit --driver-name docker

in the molecule.yml file:

  • update platforms.name, platforms.image
  • add provisioner.inventory

Starting toolset container

Make sure you have docker installed, and you can start a container with an interactive shell. If you are on Windows, run directly from PowerShell (not from WSL2) make sure the the root of the repository (git rev-parse --show-toplevel) is your current working directory

Option 1

Start the container with mounting the root directory directly in an expected collections path:

docker run --rm -v "/var/run/docker.sock:/var/run/docker.sock" -v "${PWD}:/usr/share/ansible/collections/ansible_collections/bcgov/nr" -w "/usr/share/ansible/collections/ansible_collections/bcgov/nr" -it quay.io/ansible/toolset bash

Option 2

we can start with mounting the root directory anywhere, and adding a symlink to the mounted path

docker run --rm -v "/var/run/docker.sock:/var/run/docker.sock" -v "${PWD}:/source" -w "/source"  -it quay.io/ansible/toolset bash
# after the container started, and you have a shell prompt:
mkdir -p /usr/share/ansible/collections/ansible_collections/bcgov
ln -s /source /usr/share/ansible/collections/ansible_collections/bcgov/nr

Running a specific test

The inventoy can be created once, and changes can be applied as often as you need as you work on your role/module/etc. The commands below are executed from within the toolset container previously started.

# Create inventory "machines"
molecule create --scenario-name fluent_bit

# Apply changes
molecule converge --scenario-name fluent_bit

# Destroy inventory "machines"
molecule destroy --scenario-name fluent_bit

References

nr-ansible's People

Contributors

ahbarnz-g avatar andrwils avatar bferguso avatar derekroberts avatar mbystedt avatar repo-mountie[bot] avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

nr-ansible's Issues

It's Been a While Since This Repository has Been Updated

This issue is a kind reminder that your repository has been inactive for 181 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.

To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 180 days.

  • If this product is being actively maintained, please close this issue.
  • If this repository isn't being actively maintained anymore, please archive this repository. Also, for bonus points, please add a dormant or retired life cycle badge.

Thank you for your help ensuring effective governance of our open-source ecosystem!

Liquibase/Ansible - Update the 'verify' step to stamp with release

For Liquibase/Ansible deployments, update the 'verify' action to update the Liquibase ID with the version number. (eg: verify<version_tag>) This would allow a history of 'verify's in the DATABASECHANGELOG. As it is now, a new verify removes any prior verify entries.

Add project lifecycle badge

No Project Lifecycle Badge found in your readme!

Hello! I scanned your readme and could not find a project lifecycle badge. A project lifecycle badge will provide contributors to your project as well as other stakeholders (platform services, executive) insight into the lifecycle of your repository.

What is a Project Lifecycle Badge?

It is a simple image that neatly describes your project's stage in its lifecycle. More information can be found in the project lifecycle badges documentation.

What do I need to do?

I suggest you make a PR into your README.md and add a project lifecycle badge near the top where it is easy for your users to pick it up :). Once it is merged feel free to close this issue. I will not open up a new one :)

Lets use common phrasing

TL;DR ๐ŸŽ๏ธ

Teams are encouraged to favour modern inclusive phrasing both in their communication as well as in any source checked into their repositories. You'll find a table at the end of this text with preferred phrasing to socialize with your team.

Words Matter

We're aligning our development community to favour inclusive phrasing for common technical expressions. There is a table below that outlines the phrases that are being retired along with the preferred alternatives.

During your team scrum, technical meetings, documentation, the code you write, etc. use the inclusive phrasing from the table below. That's it - it really is that easy.

For the curious mind, the Public Service Agency (PSA) has published a guide describing how Words Matter in our daily communication. Its an insightful read and a good reminder to be curious and open minded.

What about the master branch?

The word "master" is not inherently bad or non-inclusive. For example people get a masters degree; become a master of their craft; or master a skill. It's generally when the word "master" is used along side the word "slave" that it becomes non-inclusive.

Some teams choose to use the word main for the default branch of a repo as opposed to the more commonly used master branch. While it's not required or recommended, your team is empowered to do what works for them. If you do rename the master branch consider using main so that we have consistency among the repos within our organization.

Preferred Phrasing

Non-Inclusive Inclusive
Whitelist => Allowlist
Blacklist => Denylist
Master / Slave => Leader / Follower; Primary / Standby; etc
Grandfathered => Legacy status
Sanity check => Quick check; Confidence check; etc
Dummy value => Placeholder value; Sample value; etc

Pro Tip ๐Ÿค“

This list is not comprehensive. If you're aware of other outdated nomenclature please create an issue (PR preferred) with your suggestion.

Add missing topics

TL;DR

Topics greatly improve the discoverability of repos; please add the short code from the table below to the topics of your repo so that ministries can use GitHub's search to find out what repos belong to them and other visitors can find useful content (and reuse it!).

Why Topic

In short order we'll add our 800th repo. This large number clearly demonstrates the success of using GitHub and our Open Source initiative. This huge success means it's critical that we work to make our content as discoverable as possible. Through discoverability, we promote code reuse across a large decentralized organization like the Government of British Columbia as well as allow ministries to find the repos they own.

What to do

Below is a table of abbreviation a.k.a short codes for each ministry; they're the ones used in all @gov.bc.ca email addresses. Please add the short codes of the ministry or organization that "owns" this repo as a topic.

add a topic

That's it, you're done!!!

How to use

Once topics are added, you can use them in GitHub's search. For example, enter something like org:bcgov topic:citz to find all the repos that belong to Citizens' Services. You can refine this search by adding key words specific to a subject you're interested in. To learn more about searching through repos check out GitHub's doc on searching.

Pro Tip ๐Ÿค“

  • If your org is not in the list below, or the table contains errors, please create an issue here.

  • While you're doing this, add additional topics that would help someone searching for "something". These can be the language used javascript or R; something like opendata or data for data only repos; or any other key words that are useful.

  • Add a meaningful description to your repo. This is hugely valuable to people looking through our repositories.

  • If your application is live, add the production URL.

Ministry Short Codes

Short Code Organization Name
AEST Advanced Education, Skills & Training
AGRI Agriculture
ALC Agriculture Land Commission
AG Attorney General
MCF Children & Family Development
CITZ Citizens' Services
DBC Destination BC
EMBC Emergency Management BC
EAO Environmental Assessment Office
EDUC Education
EMPR Energy, Mines & Petroleum Resources
ENV Environment & Climate Change Strategy
FIN Finance
FLNR Forests, Lands, Natural Resource Operations & Rural Development
HLTH Health
IRR Indigenous Relations & Reconciliation
JEDC Jobs, Economic Development & Competitiveness
LBR Labour Policy & Legislation
LDB BC Liquor Distribution Branch
MMHA Mental Health & Addictions
MAH Municipal Affairs & Housing
BCPC Pension Corporation
PSA Public Service Agency
PSSG Public Safety and Solicitor General
SDPR Social Development & Poverty Reduction
TCA Tourism, Arts & Culture
TRAN Transportation & Infrastructure

NOTE See an error or omission? Please create an issue here to get it remedied.

Fix artifactory URL for release artifacts

The SNAPSHOT artifacts (which we've been using to date) reside in ...int/artifactory/libs-snapshot-local...
but the release artifacts reside in ...int/artifactory/libs-release/...

The URL is (can be) specified in the playbook-vars.yml file, but perhaps the framework should know the different locations for the SNAPSHOT and RELEASE arifacts.

LB - Allow chaining of schema deployments for a release

Currently if there are multiple schema deployments happening for an application release the LB playbook needs to be run once per schema. This requires more effort and time because the local_vars.yml needs to be updated for every run. Possible improvement would be:

  1. Allow a list of schemas to be provided to the playbook
  2. Modify the liquibase playbook to take a list of schemas
  3. Change the pattern so that the ansible playbook reads variables from the local_vars.yml and then local_vars_.yml
  4. Modify the liquibase role so that it takes a list of schema names
  5. Modify the liquibase role so the cd-configure and jdk roles are dependancies of the liquibase role so that those roles are initiated every time (need to confirm that the dependency would run every time)
  6. Modify the playbook to list each application config before the first run of the chained set of deployments

Note that the chained applications will only continue as long as there are no errors in any of the runs. It will stop on the first error encountered so there is no additional risk by chaining them.

It's Been a While Since This Repository has Been Updated

This issue is a kind reminder that your repository has been inactive for 604 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.

To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 180 days.

  • If this product is being actively maintained, please close this issue.
  • If this repository isn't being actively maintained anymore, please archive this repository. Also, for bonus points, please add a dormant or retired life cycle badge.

Thank you for your help ensuring effective governance of our open-source ecosystem!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.