Skip to content

List missing dependencies from an exported solution #10

@apng1982

Description

@apng1982

Use Cases:

  • Developer can validate solution locally before push a commit
  • PR validation pipeline can reject it it knows target deployment will fail

Considered supporting multiple solutions zip files, but at present can't see the point as don't have a use case for it, preferring to have a manifest for each solution and execute as required on export. (Can add this later if a requirement comes up..?) It's also very difficult because quite need to translate solution types and guides.


Should there be some sort of flag which allows the CLI to return the Dependencies object as opposed to just the string result. (Yes)

The use case would be to allow a pipeline to pipe the results into a variable and execute logic on e.g. results.count > 0

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions