You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello we are testing whether we can use autorest in our corporate environment which is very restrictive:
we can't use default npm repository but we use our own nexus server that scans all the packages for vulnerabilities
we can't access directly github.com as we are behind corporate proxy and downloading data directly from there is not allowed
Although we can change the default registry with "autorest_registry" environment variable, we can't easily override the default behavior of autorest downloading the extensions from github.com and installing them into "%USERPROFILE%.autorest" folder.
The solution seem to be that autorest would use the globally installed node modules, which can be installed from the corporate Nexus repository.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello we are testing whether we can use autorest in our corporate environment which is very restrictive:
Although we can change the default registry with "autorest_registry" environment variable, we can't easily override the default behavior of autorest downloading the extensions from github.com and installing them into "%USERPROFILE%.autorest" folder.
The solution seem to be that autorest would use the globally installed node modules, which can be installed from the corporate Nexus repository.
Would that be possible to implement?
Beta Was this translation helpful? Give feedback.
All reactions