Closed Zhirong2022 closed 1 year ago
Thanks @Zhirong2022. This issue is related to #151. There is code added to extension activation event to migrate over the legacy profile to add connectionType of "rest" so that the profiles that existed before the ssh update are properly treated as viya connections. There is also a fix to make the error message more intuitive to what's going on if a profile is encountered with an unsupported connectionType value.
Fixed on #188
@Zhirong2022 The fix has been merged to main. I was wondering if you could verify?
@smorrisj Thank you for your update. The issue has been fixed in the latest main branch.
Thanks @Zhirong2022. If its agreeable can you put the testing-complete label? Once that happens I'll close out.
Thanks @Zhirong2022. If its agreeable can you put the testing-complete label? Once that happens I'll close out.
Describe the bug Install the SAS extension package generated base on the main branch. Change profile to a valid one created before, try to Run SAS code, 'Invalid endpoint' error happened.
Steps to reproduce Steps to reproduce the behavior:
Expected behavior The error make sense or connnectionType can be added automatically for the profiles already created before
Screenshots