-
Notifications
You must be signed in to change notification settings - Fork 85
Implement Project-level defaults #1015
Copy link
Copy link
Open
Labels
apiRelated to the API.Related to the API.customerFor any bug reports or feature requests tied to customer requestsFor any bug reports or feature requests tied to customer requestsdatabaseRelated to database accessRelated to database accessnexusRelated to nexusRelated to nexus
Metadata
Metadata
Assignees
Labels
apiRelated to the API.Related to the API.customerFor any bug reports or feature requests tied to customer requestsFor any bug reports or feature requests tied to customer requestsdatabaseRelated to database accessRelated to database accessnexusRelated to nexusRelated to nexus
Type
Fields
Give feedbackNo fields configured for issues without a type.
As part of RFD 21 and the discussion on #1003, we'd like to implement defaults at the level of a Project. The canonical example from RFD 21 is a default VPC Subnet, in which we create NICs for a guest if one is not explicitly provided in the client request. Defaults should be configurable resources, at the Project scope, for example via CRUD on an endpoint like
/organizations/{org}/projects/{project}/defaults. We'll need a new table in CRDB to manage these. Below is a preliminary list of the defaults we'd like to include, but more should be added as they make sense.