Details

  • Type: New Feature New Feature
  • Status: Resolved Resolved
  • Priority: To be reviewed To be reviewed
  • Resolution: Completed
  • Affects Version/s: None
  • Fix Version/s: 0.9.2
  • Component/s: Core
  • Labels:
    None
  • Environment:

    NA

  • Configuration:
    Hide

    NA

    Show
    NA
  • Affects Docs:
    Yes
  • Similar Issues:
    None

Description

We need the ability to specify partial component configurations, which become available to users as a sort of 'virtual component'.

Reasoning: A MySQL component is great. You can create new resources based on that, but you will have to specify username and password with every resource. But IT might want to create a generic OurMySQLInstance resource, which already is pre-configured with the credentials (and a user with only limited rights, for example), but they don't want to specify the query just yet. The query (or other params) they want to leave for users to define in their own resources.

So, what to do? Let's allow the POSTing of a partial resource definition, in which some parameters are specified and some are not. The resulting, partially specialized component, should appear as available component for users to create resources on. They then only see and need to specify those parameters that have not been specified yet.

Activity

There are no comments yet on this issue.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: