UI components has to be composed with backend logic

[knatarasan]

Right now this is lifecycle of a UI aws component (eg: EC2)

• created in Canvas ( while drag& drop) + Its backend object created
• Edited in canvas + Backend updated
• Deleted in canvas + Backend delete

Required enhancement : Front end object should compose required logic to for backend operations

[sathiscode]

Prefer not to put any logic in frontend...Frontend should only be used for display purpose...we should put any required logic in the backend....we can discuss in detail

[knatarasan]

Concluded:

Plan

• graph plan

  • nodes

    • node1 : data { label: "ec2" , apiobject: server_ec2_obj }
      apiobject: serverobject_id viewpoint { specific to node icon } style

            Need for schema:
              - instance_type ( selects from drop down )
              - ip (auto assigned) , host name , instance id READ ONLY
              - SG configuration ( Free ip , http ) : free entry
              - Key pair name                         
      
      Approach : (instead of all apiobject here , just keep refrence) server obj_plan --> plan_id --> awscomp ec2

    • node1 : pg

    • node2 : lb

  • edges

• server obj plan
  • plan_id
    • awscomp ec2
    • genericcomp pg
    • awscomp lb

Conclusion :

• Move server objects into corresponding node
• Remove server obj plan