Skip to content

If checkbox is unchecked, the resource config field is not necessarily false. Provider might use some default value internally.  #16

@nmbr7

Description

@nmbr7

Notes

  • Currently the renderer doesn't have any info about the default value of any of the fields, the codegen need to support this property.
  • We can only override the field values from the UI and doesn't have any info about the default value of fields before deploying it (We can get the default value after deployment by getting the output of the resource and getting the value of the un-configured fields., this output feature is not implemented in the backend yet)
  • The codegen will have to parse description of the resource input property fields to get the default value if the respective field is available. We could make use of the the usual patterns present in the description like 'default value is ..' or 'defaults to ..' or use an LLM to parse the data for us (Will also require a way to validate LLM generated default value info).

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions