Using: https://github.com/VantageDiscovery/helm-charts/tree/main/charts/temporalio
In the Temporal chart's directory:
-
Update helm dependencies
helm dep up
| format = """ | |
| $username\ | |
| $hostname\ | |
| $directory\ | |
| $git_branch\ | |
| $git_state\ | |
| $git_status\ | |
| $git_commit\ | |
| $cmd_duration\ | |
| $line_break\ |
Using: https://github.com/VantageDiscovery/helm-charts/tree/main/charts/temporalio
In the Temporal chart's directory:
Update helm dependencies
helm dep up
| #!/bin/bash | |
| # spell:disable | |
| # setopt interactive_comments | |
| # shellcheck disable=SC2086,1090 | |
| # this file is sourced by ~/.zshrc every time a new shell is opened | |
| # downstairs computer | |
| export maxc='[email protected]' |
| # Get list of projects | |
| curl --request GET --header "PRIVATE-TOKEN: $YUM_GITLAB_TOKEN" "https://gitlab.yum.com/api/v4/projects?per_page=100&page=1" | jq '.[]' | |
| # Get list of projects and select on with id 24 | |
| curl --request GET --header "PRIVATE-TOKEN: $YUM_GITLAB_TOKEN" "https://gitlab.yum.com/api/v4/projects?per_page=100&page=1" | jq '.[] | select(.id=="24")' | |
| # Get list of projects with name search | |
| curl --request GET --header "PRIVATE-TOKEN: $YUM_GITLAB_TOKEN" "https://gitlab.yum.com/api/v4/projects?per_page=100&page=1&search=olympus" | jq '.[]' | |
| # Get list of files in root of repo |
strip --context to use current context:
kubectl config view --minify --flatten --context=kind-terraform-learn
host == clusters.cluster.server
client_certificate == users.user.client-certificate-data
client_key == users.user.client-key-data
cluster_ca_certificate == clusters.cluster.certificate-authority-data
This gist contains two different implementations of automatically appending the Jira ID to the git commit message.
I don't know if one way is better than the other. Choose one and create a file in your repo.
It must be named exactly: prepare-commit-msg (no extension) and placed in the <repo-name>/.git/hooks dir.
Very detailed discussion here: https://stackoverflow.com/questions/427207/can-git-hook-scripts-be-managed-along-with-the-repository
keytool -list -keystore /etc/pki/java/cacerts
sudo keytool -list -v -keystore cacerts > /home/engineering/keys.txt
keytool -list -v -keystore cacerts -storepass changeit | grep -i consilio
keytool -list -v -keystore cacerts -alias consilio-cert-issuer -storepass changeit
sudo keytool -keystore cacerts -import -alias consilio-certs-issuer -file /home/engineering/consilio-certs-issuer
| # These are set via $env:TF_VAR_x = $env:<var_x> | |
| variable "VRA_USER" {} | |
| variable "VRA_PASS" {} | |
| provider "vra7" { | |
| username = "${var.VRA_USER}" | |
| password = "${var.VRA_PASS}" | |
| tenant = "<tenant_name>" | |
| host = "<https://your.vra.host>" | |
| # insecure = true |