Hi all,
I want to start the discussion of removing engine registration. How many
people actually take advantage of being able to run pio commands everywhere
outside of an engine template directory? This will be a nontrivial change
on the operational side so I want to gauge the potential impact to
The Apache version is not released yet. If you can’t wait for a week or so, try
instructions here for the fork I maintain which works with old non-apache
templates: actionml.com/docs/install
On Sep 11, 2016, at 5:10 AM, babak hosseinzadeh wrote:
Hi,
I can't figure out where to download and
Which brings up the next set of issues: What do we do for Salesforce owned
SDKs? Can the SDKs be donated?
In any case I suggest we add to the “gallery” so it might be better categorized
to include SDKs, Templates, other extras like containers or whatnot. If we are
agreed about external template
This is a great discussion topic and a great idea.
However the cons must also be addressed, we will need to do this before
multi-tenant deploys can happen and the benefits are just as large as removing
`pio build`
It would be great to get rid of manifest.json and put all metadata in the store
Pat, would you explain more about the 'instanceId' as in
`pio register --variant path/to/some-engine.json --instanceId
some-REST-compatible-resource-id` ?
Currently PIO also has a concept of engineInstanceId, which is output of
train. I think you are referring to different thing, right?
Kenneth
