In the morning deployed to prod, it seems to be working; notified Renato that he can tell the customers ("client-side people") that they can do.
And started slapping together scripts, to encrypt/decrypt, to reencrypt the same keys from staging to prod, etc.
Spent the whole day scripting. Ok, it worked by the end of the day (by 22:40), but I found that what was deployed to prod does not accept my keys, for two reasons. 1: wrong regex (my fault, I did not cover it with tests), 2: seems like prod won't take my updates from France. But that's not a problem, I can ask someone in America. Anyway, just running tests on my new pr that fixes all that.
Meanwhile, we had three meetings!
1. Standup. That was easy.
2. Postmortem. That was nice, we are all good people and communicate (no kidding).
3. Planning. Oh shit, that was hell. I don't know how many times I explained that my new spike has nothing to do with encrypted signing keys, and that covers, more or less, all future demands from our "editor people"; and then Renato found some "back burner" jira case that was postponed because they wanted me to do the keys.
I was exhausted. And then, when I discovered that my updates, sent via "legal API", don't make it (ok, I could of course just write a couple of sql statements... four actually, or rather generate them), then it was a really nice outcome.
Just sent a pr for review. Oh, whatever.
And started slapping together scripts, to encrypt/decrypt, to reencrypt the same keys from staging to prod, etc.
Spent the whole day scripting. Ok, it worked by the end of the day (by 22:40), but I found that what was deployed to prod does not accept my keys, for two reasons. 1: wrong regex (my fault, I did not cover it with tests), 2: seems like prod won't take my updates from France. But that's not a problem, I can ask someone in America. Anyway, just running tests on my new pr that fixes all that.
Meanwhile, we had three meetings!
1. Standup. That was easy.
2. Postmortem. That was nice, we are all good people and communicate (no kidding).
3. Planning. Oh shit, that was hell. I don't know how many times I explained that my new spike has nothing to do with encrypted signing keys, and that covers, more or less, all future demands from our "editor people"; and then Renato found some "back burner" jira case that was postponed because they wanted me to do the keys.
I was exhausted. And then, when I discovered that my updates, sent via "legal API", don't make it (ok, I could of course just write a couple of sql statements... four actually, or rather generate them), then it was a really nice outcome.
Just sent a pr for review. Oh, whatever.