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
We populate all available instance types in the YW DB even though we only support a few of them. This causes YW issues due to instances that we don't even care about. So, we should skip over the unwanted instance types when initializing the changes.
The text was updated successfully, but these errors were encountered:
Summary:
When initializing AWS provider, all instance type information is saved. This can consume a lot of
time later and cause problems if certain AWS regions change.
Test Plan: Create AWS provider
Reviewers: arnav, ram
Reviewed By: ram
Subscribers: jenkins-bot, yugaware
Differential Revision: https://phabricator.dev.yugabyte.com/D8016
We populate all available instance types in the YW DB even though we only support a few of them. This causes YW issues due to instances that we don't even care about. So, we should skip over the unwanted instance types when initializing the changes.
The text was updated successfully, but these errors were encountered: