[Container-tools] Dev assistant implementation of nulecule spec

[Langdon White]

On 04/23/2015 09:37 AM, Aaron Weitekamp wrote:
> There has been some discussion on how DevAssistant[1] might implement the nulecule spec[2]. There are a few requirements that need to be sorted out:
>
> - a piece of data signifying that the app was created with DA/has some DA scripts that can be used with it

On the first part, I am not sure I agree, unless the 2nd part is true. 
Like, I don't think you need to indicate it was gen'd with DA (unless we 
want to for "marketing reasons"). However, I think you need a way to 
show the DA functionality that is available (if there is any)
> - location of these files in the tree
> - additional metadata like Authors, Website, Issue Tracker, Summary (a shorter version of the description) etc.
>
> It's not clear to me if we specifically call out the support of arbitrary data in the 'metadata' object[3] but I think we intend to. Could the devassistant data go in here? Could devassistant reference remote and local files via uri://<path> in this section using their own arbitrary convention? For example, file://devassistant/somefile.json or http://path/to/remote/file.json

I definitely think a core part of the spec is the ability to carry 
arbitrary metadata to "future proof" it. I think we wouldn't even be 
considering a new spec if kube allowed for arbitrary metadata that the 
interpreters weren't aware of. So, +1.

I also think the "arbitrary uri" is the part of the "arbitrary metadata" 
that should be spec'd .. so that even if there is a new thing, it is at 
least structured similarly

> [1] http://devassistant.org/
> [2] https://github.com/projectatomic/nulecule
> [3] https://github.com/projectatomic/nulecule/tree/master/spec/0.0.1-alpha#metadataObject
>
> _______________________________________________
> Container-tools mailing list
> Container-tools at redhat.com
> https://www.redhat.com/mailman/listinfo/container-tools