-
Notifications
You must be signed in to change notification settings - Fork 199
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
[Merged by Bors] - feat: fvm show
and fvm current
command
#3601
Conversation
let ver_b = Channel::parse("0.10.13").unwrap(); | ||
let ver_b = Channel::parse("0.10.13-mirroring347239873+20231016").unwrap(); |
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.
Update test to validate tags support.
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.
Overall look reasonable. Couple of questions on why additional info for manifest is necessary.
/// If theres any Active Version, the [`VersionManifest`] is not included | ||
/// as part of the first tuple value, instead it is returned as the second | ||
/// tuple value. | ||
fn scan_versions_manifests( |
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.
this should be moved to version manager or version directory
?
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.
I also thought about it but I as well, but I found the use case strongly tied to the purpose of fvm show
.
Given that this function not only takes the manifest from VersionDirectory
in the process of walking a directory, but it also puts apart the active version, so fvm show
can render the check
symbol later on.
I could move tho scan
logic to be part of VersionDirectory
and return the vector filled with all version directories, but then I would have to loop into this vector a second time to retrieve the active version and split it from the rest to provide it to fn render_table(manifests: Vec<VersionManifest>, maybe_active: Option<VersionManifest>)
.
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.
Issue is that this now has knowledge of internals of the versions, manifest. This needs to move there
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.
Got it! Migrating to VersionDirectory
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.
Here it is! 8c1db1c
@EstebanBorai after install, Not sure about subsequent versions @sehz ? |
@EstebanBorai after installation, |
Thanks for asking @ajhunyady and @sehz! In my video Im showing commands with the build of FVM I had locally. In production users will have FVM installed via our cURL In practice, users running: curl -fsS https://hub.infinyon.cloud/install/install.sh | bash Will:
With regards to setting as default after install, initially we designed a "no side effects" implementation which makes every command atomic. But I think we could introduce |
install should perform switch under the hood. You can do This feedback is on the usability not internal design decisions. Note, |
/// If theres any Active Version, the [`VersionManifest`] is not included | ||
/// as part of the first tuple value, instead it is returned as the second | ||
/// tuple value. | ||
fn scan_versions_manifests( |
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.
Issue is that this now has knowledge of internals of the versions, manifest. This needs to move there
Yes, that can be done in separate PR. But |
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.
K. LGTM. Please update install logic to switch to version in next PR
@EstebanBorai please file a new issue with left-over items and add to tracking issue #3537 so we don't lose them. |
bors r+ |
Introduces two utility commands for FVM used to check on the active version and listing installed versions. Use `fvm current` to print the active Fluvio Version and use `fvm show` to list installed Fluvio versions. ## Demo https://github.com/infinyon/fluvio/assets/34756077/a2327a63-1d9e-4ceb-86d3-02522de0aa42
Build failed: |
bors r+ |
Introduces two utility commands for FVM used to check on the active version and listing installed versions. Use `fvm current` to print the active Fluvio Version and use `fvm show` to list installed Fluvio versions. ## Demo https://github.com/infinyon/fluvio/assets/34756077/a2327a63-1d9e-4ceb-86d3-02522de0aa42
Pull request successfully merged into master. Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page. |
fvm show
and fvm current
commandfvm show
and fvm current
command
Introduces two utility commands for FVM used to check on the active version and
listing installed versions.
Use
fvm current
to print the active Fluvio Version and usefvm show
to listinstalled Fluvio versions.
Demo
CleanShot.2023-10-16.at.15.44.58.mp4