Describe the bug
On leapp cli versions 0.1.62 and 0.1.63 I am unable to start chained iam role sessions.
Coming from this thread in the slack. I don't see any github issues reported, so I'm opening one to track this bug. My situation is slightly different as I have not upgraded Leapp desktop to 0.25.x yet. I started experiencing this bug after upgrading the cli from 0.1.61 to version 0.1.63.
From the testing I have done so far, I am able to start a session with provider type AWS Single Sign-On, but a session with provider type IAM Role Chained fails with this error output:
› Error: stream.pipe is not a function
› Deserialization error: to see the raw response, inspect the hidden field {error}.$response on this object.
Leapp Version
Leapp CLI: >= 0.1.62
To Reproduce
Steps to reproduce the behavior:
create a chained iam role session
use the cli to start the chained role session: leapp session start --sessionId $id
Expected behaviorleapp session start starts a chained iam role session without erroring
Desktop (please complete the following information):
OS: MacOs (Apple Silicon M1)
OS Version 14.3
Leapp Version 0.24.4
Leapp CLI Version: >= 0.1.62
Additional context
I have tried uninstalling the leapp cli via brew brew uninstall leapp-cli and installing older versions via npm.
npm i -g @noovolari/leapp-cli@0.1.62 has the same stream.pipe error.
Current Workaround:npm i -g @noovolari/leapp-cli@0.1.61 is working for me with leapp desktop version 0.24.4
Describe the bug On leapp cli versions
0.1.62
and0.1.63
I am unable to start chained iam role sessions.Coming from this thread in the slack. I don't see any github issues reported, so I'm opening one to track this bug. My situation is slightly different as I have not upgraded Leapp desktop to 0.25.x yet. I started experiencing this bug after upgrading the cli from
0.1.61
to version0.1.63
.From the testing I have done so far, I am able to start a session with provider type
AWS Single Sign-On
, but a session with provider typeIAM Role Chained
fails with this error output:Leapp Version
To Reproduce Steps to reproduce the behavior:
leapp session start --sessionId $id
Expected behavior
leapp session start
starts a chained iam role session without erroringDesktop (please complete the following information):
Additional context I have tried uninstalling the leapp cli via brew
brew uninstall leapp-cli
and installing older versions via npm.npm i -g @noovolari/leapp-cli@0.1.62
has the samestream.pipe
error.Current Workaround:
npm i -g @noovolari/leapp-cli@0.1.61
is working for me with leapp desktop version0.24.4