Development operations ##

Development operations

A set of snippets that helped in the past.

test irods auth proxy

Create users (also in different iRODS zones) and test them with the proxy from the HTTP API:

rapydo shell icat

berods
ZONE1=$IRODS_ZONE
ZONE2=anotherZone
iadmin mkzone $ZONE2 remote

USER=paolobeta
PASS=thisisalongerpassword
iadmin mkuser $USER rodsuser
iadmin moduser $USER password $PASS
iadmin mkuser $USER#$ZONE2 rodsuser

and in another shell

rapydo shell restclient

USER=paolobeta
PASS=thisisalongerpassword
SERVER="$APP_HOST$APP_PORT"

# http POST $SERVER/auth/b2safeproxy username=$USER password=$PASS

TOKEN=$(http POST $SERVER/auth/b2safeproxy \
   username=$USER password=$PASS | jq .Response.data.token | tr -d '"')

http $SERVER/auth/b2safeproxy Authorization:"Bearer $TOKEN"

B2ACCESS proxy failing

About the B2ACCESS issue in August 2017, a grid-proxy-init on the certificate creates a valid one:

rapydo shell icat
berods

CERTUSER=somelonghash

cd $CERTDIR/$CERTUSER
cp userproxy.crt b2access.proxy.crt
export X509_USER_CERT=$CERTDIR/$CERTUSER/b2access.proxy.crt
export X509_USER_KEY=$CERTDIR/$CERTUSER/b2access.proxy.crt
grid-proxy-init -out userproxy.crt

squash branch

A better practice before pull requesting is to squash commits into a single one. Here’s a guide on how to do so with git cli:

MYEXISTINGBRANCH='v0.1.0'
BASEBRANCH='master'

# start from the base branch (usually it's master)
git checkout $BASEBRANCH
# create a new branch for squashing
git checkout -b ${MYEXISTINGBRANCH}-squashed
# squash the differences between now and the feature branch
git merge --squash $MYEXISTINGBRANCH
# commit message will contain all commit messages so far
git commit
# you may/should change the content, at least top title and description