gtristan commented on PR #2035:
URL: https://github.com/apache/buildstream/pull/2035#issuecomment-3077245975
Overall this is coming along nicely... some things which come to mind:
* We need to consider how this will eventually evolve to support
project-less use
* I.e. there is a certain amount of information which is serialized into
artifact metadata, that is extensible and can grow, and `bst inspect` should
(at least eventually) allow inspection of artifact dependency chains loaded
from a remote cache, without needing to have a local checkout of the project
* This means we need to consider whether we intend to support this
directly in `bst inspect`, or if we intend to have that as a separate addition
as `bst artifact inspect`... perhaps the latter seems more sensible
* We still do not have anything reporting of public data here as far as I
can see
* Public data is special as it is *mutable*
* We need to consider what is sensible to report here
* Initially, my feeling is that we should support reporting both original
public data and mutated public data separately
* This might require some added features to the core
* Displaying original public data is only possible if we have a local
project (not loading from a remote artifact)
* Displaying mutated public data is only possible if the element has a
locally cached artifact
* Looks like this is still missing the ability to show artifact build logs
* Perhaps not necessary for an initial implementation but shouldn't be too
hard to include
* Definitely should not be included in output by default (only if
specified on the command line *--fields*)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
