-
Notifications
You must be signed in to change notification settings - Fork 580
feat: aztec-up can be used to manage multiple aztec versions #19261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
|
a suggestion: does this make E.g., the ideal workflow (similar to gaztec): bash -i <(curl -s https://install.aztec.network)
aztec --version
#> 2.1.9 # the latest version by default
echo 3.0.0 > .aztecrc
aztec --version
#> 3.0.0
# in another project
echo 3.0.0-devnet.5 > .aztecrc
aztec --version
#> 3.0.0-devnet.5Note that This mimics how |
ec9d893 to
d28e3da
Compare
37c2b1a to
13a3485
Compare
b94f1ff to
d10ef23
Compare
17ad593 to
ad42667
Compare
d10ef23 to
d6c115a
Compare
a35138c to
110f422
Compare
d6c115a to
d213ad3
Compare
4996807 to
0556d70
Compare
163b2aa to
8e792d8
Compare
0556d70 to
3075d4a
Compare
8e792d8 to
ab988be
Compare
3075d4a to
f92cdcb
Compare
beef6e1 to
a85f821
Compare
62c24b9 to
0451dec
Compare
a85f821 to
530d114
Compare
Flakey Tests🤖 says: This CI run detected 4 tests that failed, but were tolerated due to a .test_patterns.yml entry. |
cd2bf56 to
0ffc1e0
Compare
b94556e to
7a9085a
Compare
| @auth.verify_password | ||
| def verify_password(username, password): | ||
| if username == "aztec" and password == "letmeseethoselogs": | ||
| if username == "aztec" and password == DASHBOARD_PASSWORD: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
luckily there's probably no overlap between github farmers and API-probing bots
| case $cmd in | ||
| test) | ||
| export LOG_LEVEL="${LOG_LEVEL:-info}" | ||
| export LOG_LEVEL="${LOG_LEVEL:-error}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm not having LOG_LEVEL=info is clean but I wonder if it will make it harder when people report their issues
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unless I'm missing something, I thought the TXE should basically be operating transparently. It's obviously useful to see error messages, but INFO is basically debug in this context right? It's nargo that's giving all the useful feedback? Trivial to revert later if needed.
| # This script is called by aztec-up to install a specific version of the Aztec toolchain. | ||
| # It expects VERSION and INSTALL_URI to be set. | ||
| set -euo pipefail | ||
| shopt -s inherit_errexit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: At first guess I would say 0.0.1/install is not the current source
7d4e6cd to
d041e39
Compare
d041e39 to
c7e2941
Compare
f942892 to
a349f20
Compare
`aztec-up` can be used to manage multiple versions. ``` $ aztec-up aztec-up - Aztec version manager Usage: aztec-up [command] [options] Commands: install <version> Install a version and switch to it use [<version>] Switch to an installed version (or read from .aztecrc) list List installed versions uninstall <version> Remove an installed version self-update Update aztec-up itself to the latest version Options: -h, --help Show this help message Examples: aztec-up install Install the latest version aztec-up install nightly Install the latest nightly version aztec-up install 0.85.0 Install a specific version aztec-up use 0.85.0 Switch to version 0.85.0 aztec-up use Read version from .aztecrc and switch to it aztec-up list Show all installed versions aztec-up self-update Update aztec-up to latest ``` If a `.aztecrc` file is present in the cwd, `aztec` will automatically switch to that version in that run context. ``` t % aztec --version 0.0.1-commit.1142ef1 t % cd fooproj t % cat .aztecrc 0.0.1-commit.6d3c34e t % aztec --version 0.0.1-commit.6d3c34e t % ``` # Testing You can install `aztec-up` with: ``` VERSION=0.0.1-commit.6d3c34e bash -i <(curl -s https://install.aztec.network/0.0.1-commit.6d3c34e/aztec-install) ``` At present you can't list available remote versions. The code does currently support listing available remote aliases, but they're not deployed yet. You can install another version with e.g. ``` aztec-up install 0.0.1-commit.1142ef1 ``` Then list versions with: ``` t % aztec-up list Installed versions: * 0.0.1-commit.1142ef1 (current) 0.0.1-commit.6d3c34e Aliases: (could not fetch aliases) ```
a349f20 to
f69c7bf
Compare

aztec-upcan be used to manage multiple versions.If a
.aztecrcfile is present in the cwd,aztecwill automatically switch to that version in that run context.Testing
You can install
aztec-upwith:At present you can't list available remote versions. The code does currently support listing available remote aliases, but they're not deployed yet. You can install another version with e.g.
Then list versions with: