Enhancement to Components: Configuration property

[leecalcote]

Current Behavior

In adherence to Meshery Model's design principles:

1. Treat 3rd-party-authored content/manifests/schemas as hermetically sealed objects.
2. Treat all Definitions similarly within Meshery’s object model.

Components need a way of capturing declared configuration.

Implementation

1. Move “configuration” from Designs to Components (

   schemas/schemas/constructs/v1beta1/designs.json

   Lines 54 to 58 in a7561a7

   	"configuration": {
   	"$comment": "The configuration of the component. The configuration is based on the schema defined within the component definition.",
   	"additionalProperties": {
   	"type": "string"
   	},

   )
2. Move “id” from Designs to Components (

   schemas/schemas/constructs/v1beta1/designs.json

   Lines 23 to 26 in a7561a7

   	"additionalProperties": {
   	"type": "string",
   	"format": "uuid"
   	},

   )

---

Contributor Guides and Handbook

• 🛠 Meshery Build & Release Strategy
• 📚 Instructions for contributing to documentation
  • Meshery documentation site and source
• 🎨 Wireframes and designs for Meshery UI in Figma
• 🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

[Aviral0702]

Can I take up this issue ?