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
{{ message }}
This repository has been archived by the owner on May 6, 2022. It is now read-only.
When exporting the latest API proxy revision, it would be convenient if the zipfile did not append the revision number.
For example if the latest revision of myproxy-v1 is 7, the proxy is exported as: myproxy-v1_7.zip
Upon importing that API proxy bundle the resultant proxy is named myproxy-v1_7.
This will cause problems for any API product that uses myproxy-v1.
This would facilitate org-to-org migration without any intervening renaming.
Obviously, this doesn't apply when exporting all proxies via --all.
The text was updated successfully, but these errors were encountered:
When exporting the latest API proxy revision, it would be convenient if the zipfile did not append the revision number.
For example if the latest revision of
myproxy-v1
is 7, the proxy is exported as:myproxy-v1_7.zip
Upon importing that API proxy bundle the resultant proxy is named
myproxy-v1_7
.This will cause problems for any API product that uses
myproxy-v1
.This would facilitate org-to-org migration without any intervening renaming.
Obviously, this doesn't apply when exporting all proxies via
--all
.The text was updated successfully, but these errors were encountered: