Ansible : GCP Google Cloud (Compute) ansible dynamic inventory with cache

Inventory definition GCP compute

---

plugin: google.cloud.gcp_compute

# https://docs.ansible.com/ansible/latest/collections/google/cloud/gcp_compute_inventory.html

# https://gitlab.com/gitlab-org/gitlab-environment-toolkit/-/blob/main/docs/environment_configure.md#google-cloud-platform-gcp

projects:

- project_id

auth_kind: serviceaccount

# must match `ansible_user` below, cf. other article on how to set this up

service_account_file: ./gcp-sa.json

filters:

# only return running instances, we won't be able to connect to sopped instances

- status = RUNNING

# for example, only return compute instances with label foo = foobar

- labels.foo = foobar

keyed_groups:

- key: labels

prefix: label

hostnames:

- name

- public_ip

- private_ip

compose:

#<ansible variable to be set> <data from gcp discovery>

# Set an inventory parameter to use the Public IP address to connect to the host

#ansible_host: public_ip

ansible_host: networkInterfaces[0].accessConfigs[0].natIP

ansible_user: "'sa_115528571027174573787'"

# GCP compute label "activate_this" value => ansible variable "run_this" value

run_this: labels['activate_this']

Wiki Patterns and Anti-Patterns - Stewart Mader / Confluence

 observed on Confluence wiki, but can actually be applied for every wiki

The overall goal is to go from generally observed usage 90-9-1 to 80-16-4 
(lurker - occasional contribution - frequent contribution)

https://www.stewartmader.com/wikipatterns/

Wikipatterns offers practical, proven advice for guiding adoption of new technology, featuring case studies from Apple, Johns Hopkins, LeapFrog, and the nonpartisan National Constitution Center. Drawing from A Pattern Language, the architecture and urban design book by Christopher Alexander, Sara Ishikawa, and Murray Silverstein, Wikipatterns enables you to build an enduring, useful space for collaboration, whether your team is nearby or spread around the world. Reviews | Order a Copy

Patterns & Anti-Patterns

• 90-9-1 – Online participation generally follows a 90-9-1 ratio of readers to contributors
• Acknowledge – Empower peer recognition and encourage its use
• Ambassador – Person who helps adoption through their endorsement and consistent promotion
• BarnRaising – Designated time to build structure, seed content, and set norms
• BlankPage – Seed new pages with structure or content to guide others
• Bully – Someone who goes too far in pushing people to use the wiki
• Champion – Provides guidance, reduces obstacles, and is essential to the success of adoption
• Charter – Guidelines for collaboration should be created at the start of technology adoption
• FAQ – Scaffold that enables a group to build information and share answers
• Gnome – Performs small edits on a wiki to continually improve its overall quality
• IntentionalError – Make some mistakes for others to find and fix, thus getting them used to editing
• Invitation – Good way to encourage non-early adopters to get involved
• Magnet – Entice people to visit the wiki by exclusively posting essential information
• Patron – Leader who confers legitimacy that can increase the likelihood of success
• Sandbox – “Practice” page that may inadvertently hinder adoption
• Scaffold – Give people a place to start by “framing” the content that should be added to a new page
• Spectator – Someone who consumes wiki content but does not contribute to it
• Troll – Provokes the community instead of focusing criticism on specific procedural or functional issues
• Viral – Use spreads as people encourage colleagues to use the wiki