Skip to content

Instantly share code, notes, and snippets.

cd azure-docs
git pull fork
git branch --remote --merged | grep -vE '^\*|master$|origin' | sed -e 's% *fork/%%' | xargs -I % git push --delete fork %
cd ../azure-docs.ja-jp
git pull fork
git branch --remote --merged | grep -vE '^\*|master$|origin' | sed -e 's% *fork/%%' | xargs -I % git push --delete fork %
cd ../azure-docs.cs-cz
git pull fork
git branch --remote --merged | grep -vE '^\*|master$|origin' | sed -e 's% *fork/%%' | xargs -I % git push --delete fork %
cd ../azure-docs.de-de
cd azure-docs
git pull origin master; git push fork master
cd ../azure-docs.ja-jp
git pull origin master; git push fork master
cd ../azure-docs.cs-cz
git pull origin master; git push fork master
cd ../azure-docs.de-de
git pull origin master; git push fork master
cd ../azure-docs.es-es
git pull origin master; git push fork master
@changeworld
changeworld / example code
Created February 5, 2019 00:45
Workaround for overwriting environment variables in Azure DevOps
Plan A: Define the variable in the file at a more specific level, rather than at the root of the file.
jobs:
- job: a
variables:
myvariable: my value defined in the file
pool: default
steps:
- script: echo myvariable=$(myvariable)
@changeworld
changeworld / log
Created August 31, 2017 01:17
Terraform with CDN profile plan and apply output
== terraform plan run log ==
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.
The Terraform execution plan has been generated and is shown below.
Resources are shown in alphabetical order for quick scanning. Green resources
will be created (or destroyed and then created if an existing resource
exists), yellow resources are being changed in-place, and red resources
@changeworld
changeworld / error log
Created August 28, 2017 04:46
Terraform with Resource Group apply error
== terraform plan run log ==
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.
The Terraform execution plan has been generated and is shown below.
Resources are shown in alphabetical order for quick scanning. Green resources
will be created (or destroyed and then created if an existing resource
exists), yellow resources are being changed in-place, and red resources
will be destroyed. Cyan entries are data sources to be read.
@changeworld
changeworld / error log
Created August 23, 2017 04:22
Terraform with Key Vault apply error
1 error(s) occurred:
* azurerm_key_vault.test: 1 error(s) occurred:
* azurerm_key_vault.test: keyvault.VaultsClient#CreateOrUpdate: Invalid input: autorest/validation: validation failed: parameter=vaultName constraint=Pattern value="abcdefghijklmnopqrstuvwxyz" details: value doesn't match pattern ^[a-zA-Z0-9-]{3,24}$
Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.