Articles, notes and random thoughts on Software Development and Technology
Previous script for setting git branch in bash shell is here.
For zsh, here’s an approach from this gist – add to your ~/.zshrc:
function parse_git_branch() {
git branch 2> /dev/null | sed -n -e 's/^\* \(.*\)/[\1]/p'
}
COLOR_DEF=$'\e[0m'
COLOR_USR=$'\e[38;5;243m'
COLOR_DIR=$'\e[38;5;197m'
COLOR_GIT=$'\e[38;5;39m'
setopt PROMPT_SUBST
export PROMPT='${COLOR_USR}%n ${COLOR_DIR}%~ ${COLOR_GIT}$(parse_git_branch)${COLOR_DEF} $ '
Tags are useful to mark specific versions or releases of your code in a repo on a given branch. To tag everything on the current branch, use:
git tag new-tag-name
To push a new tag to a remote repo, you can either push all tags (which is not recommended):
git push remote-name --tags
or push a specific tag:
git push remote-name tag-name
More example in this SO question.
Typical Cloudformation for an S3 bucket with block all public access enabled:
Resources:
S3BucketExample:
Type: AWS::S3::Bucket
Properties:
BucketName: s3-bucket-name
PublicAccessBlockConfiguration:
BlockPublicAcls: true
BlockPublicPolicy: true
IgnorePublicAcls: true
RestrictPublicBuckets: true
If you create a Java Lambda with the provided template, you’re probably returning a response using the provided ApiGatewayResponseClass. If you run your Lambda locally with ‘serverless invoke local –function functioname’, you’ll see a response like this:
Serverless: Invoke invoke:local Serverless: In order to get human-readable output, please implement "toString()" method of your "ApiGatewayResponse" object. com.serverless.ApiGatewayResponse@3bd3d05e
Any other logger output will appear in your console, but in order to see the actual content of your ApiGatewayResponse, add a toString() method as the message suggests.
You include any of the properties in ApiGatewayResponse, but if you’re just interested in the JSON payload in the body of the response, then just adding this will return the body:
public String toString(){
return this.body;
}