-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
rdk upgrade conflicting dependency #7994
Comments
Hi @choman, thanks for reaching out. Updating the pinned PyYAML version is something that has been requested in the past, and is on the team's radar. There is both a tracking issue and open PR for this. I'd encourage you to add your use case in one or both of those issues. In the meantime, the easiest workaround would be to update to AWS CLI v2, which does not use PyYAML, so you could use 6.0 to meet the RDK dependency. Hope that helps, and please let me know if you have any follow-up questions. |
Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one. |
Thanks, did not know there was an awscli2. I will look into it |
|
Describe the issue
While using pip to upgrade to the latest rdk (was rule development kit), there becomes a round-robin of conflicting
dependencies.
Currently on rdk==0.9 and awcli==1.27.62
When upgrading to rdk==0.15 (latest as of 2023-06-22), it complains that two dependencies versions are conflicting
for awscli
Naturally, one then upgrades awscli to 1.27.158. This resolves the boto3 issue, however this is where the round-robin
issue begins.
the latest rdk==0.15 requires pyyaml > 6.0
the latest awscli==1.27.158 requires pyyaml <5.5,>=3.10
Additional Information/Context
No response
CLI version used
1.27.X
Environment details (OS name and version, etc.)
Ubuntu 23.04
The text was updated successfully, but these errors were encountered: