-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
addon status and preflight check #258
Conversation
porter/v1/addons.proto
Outdated
// ADDON_STATUS_INFRA_PROVISIONING_FAILED is the status when an addon can't be installed due to a failed infrastructure reprovisioning | ||
ADDON_STATUS_INFRA_PROVISIONING_FAILED = 4; | ||
// ADDON_STATUS_DEPLOYING is the status when an addon is being deployed | ||
ADDON_STATUS_DEPLOYING = 5; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this be ADDON_STATUS_INSTALLED? when the frontend makes the query, it wants to know whether a model is installed, after which it can render the deployment status
// deployment_target_identifier is the object that identifies the deployment target for the addon | ||
// If cluster_id is specified and deployment_target_identifier is not, then the default deployment target for the provided cluster will be used | ||
DeploymentTargetIdentifier deployment_target_identifier = 3; | ||
AddonType addon_type = 4; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should take in the entire addon config. example is if we ever want to expose the instance type of the deepgram addon to client, that will require different quotas
No description provided.