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
This is an initial step towards full support (#344), specifically only targeting the necessary plugin modifications.
RPC Changes
We will modify paragliderpb.proto to expose a new RPC which "attaches" resources to the paraglider deployment. The request will require a paraglider deployment, a resource name, and a URI for the resource. This is semantically different than CreateResource given that the service the user is aiming to add to Paraglider already exists.
Plugin Implementation
The plugin implementation of AttachResource will take the provided URI and determine if it is a multitenant service. If so, it will provision a private endpoint in the paraglider VPC in the region specified by the URI and attach it to the service. It will then create a security group (in alignment with Paraglider CreateResource expectations) and attach it to the private endpoint.
The text was updated successfully, but these errors were encountered:
This is an initial step towards full support (#344), specifically only targeting the necessary plugin modifications.
RPC Changes
We will modify paragliderpb.proto to expose a new RPC which "attaches" resources to the paraglider deployment. The request will require a paraglider deployment, a resource name, and a URI for the resource. This is semantically different than CreateResource given that the service the user is aiming to add to Paraglider already exists.
Plugin Implementation
The plugin implementation of AttachResource will take the provided URI and determine if it is a multitenant service. If so, it will provision a private endpoint in the paraglider VPC in the region specified by the URI and attach it to the service. It will then create a security group (in alignment with Paraglider CreateResource expectations) and attach it to the private endpoint.
The text was updated successfully, but these errors were encountered: