Skip to content
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

Update ROM VBNV name by reading shell version from AWS interface #8728

Merged
merged 1 commit into from
Jan 30, 2025

Conversation

karthdmg-xilinx
Copy link
Collaborator

Problem solved by the commit

The version strings for AWS are currently static.
AWS request is to show the rom vbnv name with version loaded that can change in future for F2 instance.
Added code to query the aws shell version from aws api and update rom vbnv name accordingly.

Bug / issue (if any) fixed, which PR introduced the bug, how it was discovered

The version strings for AWS are currently static.
AWS request is to show the rom vbnv name with version loaded that can change in future for F2 instance.
Added code to query the aws shell version from aws api and update rom vbnv name accordingly.

How problem was solved, alternative solutions (if any) and why they were rejected

Added code to query the aws shell version from aws api and update rom vbnv name accordingly.

Risks (if any) associated the changes in the commit

None

What has been tested and how, request additional testing if necessary

Verified the shell version from aws api is included as part of vbnv name.

Documentation impact (if any)

None

@chvamshi-xilinx chvamshi-xilinx merged commit 8af01d3 into Xilinx:2024.1 Jan 30, 2025
13 of 19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants