Impact
Analyze impact of metadata changes across packages
sfp impact package
Figures out impacted packages of a project, due to a change from the last known tags
USAGE
$ sfp impact package --basebranch <value> [--json] [--loglevel
trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
FLAGS
--basebranch=<value> (required) The base branch on which the git tags should be used
--loglevel=<option> [default: info] logging level for this command invocation
<options: trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL>
GLOBAL FLAGS
--json Format output as json.
DESCRIPTION
Figures out impacted packages of a project, due to a change from the last known tagssfp impact releaseconfig
Figures out impacted release configurations of a project, due to a change,from the last known tags
USAGE
$ sfp impact releaseconfig --basebranch <value> [--json] [--loglevel
trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL] [--branch <value>] [--directory <value>]
[--explicitDependencyCheck] [--filterBy <value>] [--filterByChangesInBranch] [--skipDiff]
FLAGS
--basebranch=<value> (required) The base branch on which the git tags should be used from
--branch=<value> The branch on which the comparison is carried out
--directory=<value> [default: config] Path to the directory containing release defns
--explicitDependencyCheck [Deprecated, no-op] dependencyOn and dependencyOnDomains are now always honored. Flag
retained for backwards compatibility.
--filterBy=<value> Filter by a specific release config name
--filterByChangesInBranch Filter packages by changes with the provided branches as opposed to tags
--loglevel=<option> [default: info] logging level for this command invocation
<options: trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL>
--skipDiff Skip diff detection and treat all packages as impacted
GLOBAL FLAGS
--json Format output as json.
DESCRIPTION
Figures out impacted release configurations of a project, due to a change,from the last known tags