rohityadavcloud commented on PR #131: URL: https://github.com/apache/cloudstack-cloudmonkey/pull/131#issuecomment-1517278045
Thanks @borisstoyanov @nvazquez - I think the fix can be simply: - If cache is available for a profile, then load it and use it - If cache isn't available for a profile, then log a warning message (to stderr) to run the sync command but fallback to the default/inbuilt cache I was also thinking, what about stale and old caches. For example, I think in the login or API response do we send the ACS version - perhaps another minor idea could be to prompt the user will same message (of running sync) if the API cache is of a different ACS version than the ACS version to which an API call has been made. (just a though) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
