Add connection interface schema + types #6
Conversation
Signed-off-by: Guillaume Falourd <guillaume.falourd@zup.com.br>
| type: aws-ecs-conn | ||
| outputs: | ||
| - name: autoscaling_capacity_providers | ||
| type: json |
There was a problem hiding this comment.
Vamos realmente ter atributos complexos (object e list)? Se for ter não deveríamos descrever quais são os atributos desses objetos complexos?
There was a problem hiding this comment.
@GuillaumeFalourd algum atualização ?
| "type": { | ||
| "type": "string", | ||
| "enum": [ | ||
| "aws-ecs-conn", |
There was a problem hiding this comment.
como vamos trabalhar a questao de novos tipos? geramos uma nova versao?
There was a problem hiding this comment.
@GuillaumeFalourd algum atualização ?
Signed-off-by: Guillaume Falourd <guillaume.falourd@zup.com.br>
Signed-off-by: Guillaume Falourd <guillaume.falourd@zup.com.br>
Signed-off-by: Guillaume Falourd <guillaume.falourd@zup.com.br>
| schemaVersion: v1 | ||
| kind: connection-interface | ||
| metadata: | ||
| name: AWS RDS CONNECTION INTERFACE |
There was a problem hiding this comment.
Acho q o name e o display name estão invertidos.
A ideia do name é o que exibiria no CLI ou o usuário digitaria via linha de comando.
O Display name seria algo mais friendly pra exibição em telas.
O name no caso tb acaba fazendo um papel de slug, caso seja necessário o usuário final referenciar escrevendo.
| "type": { | ||
| "type": "string", | ||
| "enum": [ | ||
| "null", |
| version: 1.0.0 | ||
| picture: connection.png | ||
| spec: | ||
| type: aws-ecs-conn |
There was a problem hiding this comment.
O Type seria um enum fixo?
Ou o type já poderia ser o name do connection interface?
Signed-off-by: Guillaume Falourd guillaume.falourd@zup.com.br
aws-ecs-connconnection interface type.aws-rds-connconnection interface type.Related to https://github.com/stack-spot/runtime-engine-api/issues/30
Other types could be created following https://github.com/orgs/terraform-aws-modules/repositories specifications.