(disclamer, I work for 1Password)

I can tell you a "secret" you can download any version of 1Password, including version 3 from this website: https://app-updates.agilebits.com/

I know it was announced already here, but I think this deserves separate post

[I work for 1Password] 1Password is not competing with Vault. In fact we have very good relationships and mutual respect with HashiCorp on many levels.

Also Secret automation integrates (acts as a provider) with HC Vault[0]

0: https://github.com/1Password/vault-plugin-secrets-onepasswor...

[I work for 1Password]

1Password is not competing with Vault. In fact we have very good relationships and mutual respect with HashiCorp on many levels.

Also Secret automation integrates (acts as a provider) with HC Vault[1]

1. https://github.com/1Password/vault-plugin-secrets-onepasswor...

you can do similar things with 1Password CLI.

Here is short example: https://github.com/stumyp/ope

Kind of reminds me of Murphy's law:

1. Things get worse before they get better. 2. Who said things would get better?

Disclaimer: I work for AgileBits.

CloudFormation is a great tool, don't get us wrong. It is one of the first cloud IaaC tools.

And it has it's downsides:

- inability to address specific object in the state, similar to `-target ` option in terraform

- forcible re-deployment (`taint`ing) of the resouce is not possible too, well, not as easy as in TF

- when creating ChangeSet in CF, it is absolutely useless on nested stacks, all you see in it is "Stack will be updated", even if there is nothing to update

- targeted `destroy`s do not exist, as well as destroy `plan`s: similar to what `terraform plan -out plan.out -destroy -target aws_resource.name; terraform apply plan.out` does

- The work with state, renaming, reassigning, deleting and importing resources is missing in CF as a class

- TF refreshes state of the resources each run, checking their actual state and trying to revert any changes applied to them outside of the flow, CF assumes that nothing is changed and gets very surprised when it is drifted or simply doesn't match its expectations. ( I know there is drift detection, but does it actually restores the desired state? I've never had a chance to check that..)

When we deployed new TF stack, we imported part of the resources created by old CF template. And now I am a bit worried to clean it up, because it might try to delete old resources, even with '"DeletionPolicy": retain'. I have no visibility or control over its action. Basically: apply the template and pray.

ChageSets also failed me once, trying to do not what it was telling me in the plan. Terraform plan once captured into the file will do exactly what it promised me, when applied.

To sum up: both tools got their 'pro-'s and 'con-'s, and personally I feel more comfortable with the Terraform.

Because we needed to re-deploy our database, which unfortunately requires downtime.

Everything described in the blog post is using modules making infrastructure description abstract enough to understand and deploy/manage.

They are completely independent, that was the goal.