We always had this dream back in Canada: retire to Europe, “ideally somewhere south”. This post is about how that plan half-worked, twenty years early, and how it landed us in Bratislava instead.
How Valencia actually happened (it was never a plan) # In 2012 we did our first ever trip to Spain (Madrid → Valencia → Barcelona), triggered by our daughter’s stay in Madrid. It was part of the student exchange where Silvia spent 3 months with a Spanish family in Madrid and we had a Spanish girl from that family with us in Ottawa. We loved the experience - it was different than Italy we knew, but intriguing. So we started to consider Spain as a possible retirement destination.
The last post here is dated February 18, 2021. It was a perfectly ordinary how-to about Bitbucket permissions, and nothing about it suggested it would be the last one for five and a half years. There was no farewell post, no “taking a break” announcement. The blog just — stopped.
This post is the missing announcement, written from the other side.
What happened # The short version: life kept running, and the writing habit didn’t.
How to manage users and groups in Bitbucket # Use case:
I want to maintain users and groups and their access to repositories in an organization in Bitbucket. To make sure I do not miss newly changed admin access, I want to use the Bitbucket API to retrieve the list of permissions on repository basis and on user/group bases.
Mirroring large number of GitHub or Bitbucket repositories # Use case:
I want to create local clone of a large number of repositories from an organization in GitHub / Bitbucket.
Assumptions # user has SSH key registered with the GH / BB - can clone using ssh protocol user has successfully cloned at least one repo from command line before (the /etc/hosts contains host entries for BB and GH) user has modern version of Python 3 installed (3.6 or better) user has local installation of a reasonably modern Git Steps # First I use the ./bb-repo-links.sh and ./gh-repo-links.sh to generate list of repositories. See these blog articles: How to list repositories in Bitbucket and How to list repositories in github
How to list repositories in GitHub # Use Case:
I want to maintain repositories in an organization in GitHub. To make sure I do not miss newly added ones, I want to use API access to retrieve the list of repositories in the organization.
Setup # GitHub requires a token to access the API. This token is stored in an environment variable github_token and can be generated in the user profile section - settings - developer settings.
How to list repositories in Bitbucket # Use case:
I want to maintain repositories in an organization in Bitbucket. To make sure I do not miss newly added ones, I want to use API access to retrieve the list of all repositories in the organization.
Setup # Bitbucket requires a username and password to access the API. This information is stored in the environment variables BBUSER and BBPASSWORD. The BBPASSWORD should be an access token / app password defined in the App passwords section of the user settings:
This blog post is a de-powerpointized version of a brownbag session in Pivotree. The goal was to increase awareness of tools and techniques for information / knowledge capture in the projects, specifically focusing on producing quality documentation so that everybody in project can access it and contribute to it, not only developers. We wanted to look at the tools that would allow engineers keep using their tools of trade (without impact on developer’s productivity) and at the same time make the information available without duplication of work to increase re-findability of information.
Many shapes of Architecture # According to the wise people, an architecture is the shared understanding that the expert developers/system builders/maintainers have of the system design. It’s purpose is to maximize the probability that the decisions you have to make early in a project are the right ones. It is sort of a blueprint for the future system and captures parts, relations, boundaries, constraints.
I had an opportunity to attend DockerCon 2018 in person - it was great experience in wonderful city - Barcelona. My notes from it are here. I missed previous year (for variety of reasons), but DockerCon this year (as many other tech events) was purely virtual so I was able to see some part of it.
Compared to 2018, the general tone and content of this DockerCon was quite different. In 2018 it felt like all the attention is focused on big enterprise (mainly Microsoft related) and what Docker as a company is looking for best way how to hook big firms with deep pockets.
First step is to get your personal token. Log on to Terraform Cloud, go to https://app.terraform.io/app/settings/tokens and generate new token.
Note: it is important to save the token to safe place - this is only time you will see it.
Export the token:
export TFE_TOKEN=<THE-TOKEN-VALUE> The documentation for Terraform API is here
It is OK documentation but not the greatest one, however. There are two versions of the API - v1 and v2 and this is not clearly described. It could also used better examples.