Homebrew tap for the Envato port of the aws-vault by 99designs/ByteNess too.
brew install envato/envato-aws-vault/<formula>
Or brew tap envato/envato-aws-vault and then brew install <formula>.
brew help, man brew or check Homebrew's documentation.
- Make sure you are working in the actual homebrew tap directory, likely
/opt/homebrew/Library/Taps/envato/homebrew-envato-aws-vault - Open a PR with the update, something like:
brew bump-formula-pr --url https://github.com/envato/aws-vault/archive/refs/tags/v<VERSION>.tar.gz --version <VERSION>+envato --no-forkfrom the Formula directory should do the trick. It will do commits and pull-requests on your behalf, so maybe try with-nfirst to see what it's going to do. - Ensure the tests pass on the PR
- When ready, don't merge the PR. Instead, label it with
pr-pull. - This will trigger the "Publish" workflow, which will automatically merge the updates and close the PR.
- You may wish to add additional build architectures to the Formula:
- Download the bottle for the appropriate releases from the homebrew-envato-aws-vault repository Releases, E.g. the 5.1.0+envato bottle
- Unpack it in a tmp directory, make sure you remove all of the attributes that apple scribbles on it (ls -l will show an @ next to a file with an attribute)
xattr -r -d <attribute - globs don't work> <directory>for each attribute you find should do the trick. - Download the approriate release/architecture binary from the envato/aws-vault repository Releases, E.g. the 5.1.0+envato arm64 binary
- Remove all of the attributes that apple has added to your scary downloaded executable. Something like:
xattr -l aws-vault-darwin-arm64to list em all andxattr -d com.apple.quarantine aws-vault-darwin-arm64 && xattr -d com.apple.macl aws-vault-darwin-arm64 && xattr -d com.apple.metadata:kMDItemWhereFroms aws-vault-darwin-arm64should do the trick. Do keep in mind you are removing Apples malware protection from these downloads so make 100% sure you got them from github and the correct repository. - Replace the
aws-vault/5.1.0+envato/bin/aws-vaultbinary in the unpacked bottle with your new architecture, make sure you leave it with 555 permissions. - Tar up the new bottle, the name should be the same as the one you downloaded above with the insertion of arm64 before the macos release. E.g.
tar zcvf aws-vault-5.1.0+envato.arm64_monterey.bottle.tar.gz aws-vault - Get the SHA256 checksum for your shiny new manually created bottle: E.g.
sha256sum aws-vault-5.1.0+envato.arm64_monterey.bottle.tar.gz. - Edit the release of the appropriate homebrew-envato-aws-vault release and upload the new bottle you just made, the link for the 5.1.0+envato example we have been using is here.
- Edit the
Formula/aws-vault.rbfile to add a reference to your new bottle and push your change to the main branch. Your edit should look something like this commit. This file is linted so pay attention to the lining up of the fields and make sure you add the arm64 bottle before plain bottle. - Test by doing a pull on your homebrew-envato-aws-vault tap repository and then test the upgrade by running
brew upgrade aws-vault. - Swear about the fact that no-one has figured out how to make the homebrew github actions do this manual crap for us and resolve to figure it out and commit the changes here.
- Put that in the too much hassle basket and just do it manually next time.