TheBusyBiscuit

This Issue is part of Hacktoberfest - A yearly event which encourages participation in the open-source community. Sign up on their website and submit four pull requests during october (Oct 1st - Oct 31st) to any public open-source project on GitHub and earn a limited-edition T-shirt or plant a tree!

🔎 Scope

The following bullet points explain what the scope of this feature should be. It should give a general idea of what we want, you can of course deviate from this as needed.

• what is wanted or expected

⚓ Difficulty

Here is our honest estimate on how difficult (on a scale of 1-5) the implementation may be:

shortjared

a4b.amazonaws.com
access-analyzer.amazonaws.com
account.amazonaws.com
acm-pca.amazonaws.com
acm.amazonaws.com
airflow-env.amazonaws.com
airflow.amazonaws.com
alexa-appkit.amazon.com
alexa-connectedhome.amazon.com
amazonmq.amazonaws.com

matthewzring

Markdown Text 101

Want to inject some flavor into your everyday text chat? You're in luck! Discord uses Markdown, a simple plain text formatting system that'll help you make your sentences stand out. Here's how to do it! Just add a few characters before & after your desired text to change your text! I'll show you some examples...

What this guide covers:

• Text Formatting
• Organizational Text Formatting
  • Headers
• Masked Links

willejs

Moving Concourse Pipelines

Currently concourse does not support moving pipelines between teams via fly CLI. There is an issue for that here

The only way to do this is to make a few changes in the DB.

If you run the statement below you will see that 6 tables have the team_id column.

concourse=> select table_name                                                                                                                                                                                                                                                                                                                                                       from INFORMATION_SCHEMA.COLUMNS                                                                                                                                                                                                                                                                            

cezaraugusto

For troubleshooting, two things to first try:

run `git config --global gpg.program gpg2`, to make sure git uses gpg2 and not gpg
run `echo "test" | gpg2 --clearsign`, to make sure gpg2 itself is working
If that all looks all right, one next thing to try:

run `brew install pinentry` to ensure you have a good tool installed for passphrase entry
If after that install and you re-try git commit and still get the "failed to sign the data" error:

run `gpgconf --kill gpg-agent` to kill any running agent that might be hung

woowa-hsw0

#!/bin/bash

set -eu
umask 0022

if [[ $# -lt 1 ]]; then
    echo "Usage: $0 role_name [AWS ACCOUNT NUMBER]" >&2
    exit 1
fi