Add deployment-scope param for alizer CLI #1172
Labels
area/alizer
Enhancement or issue related to the alizer repo
demo
Issue or PR candidate for a demo at the end of the Sprint
lifecycle/rotten
Rotten items. These items have been stale for 60 days and are now closed.
lifecycle/stale
Stale items. These items have not been updated for 90 days.
status/blocked
Which area/kind this issue is related to?
/area alizer
Issue Description
As mentioned in the proposal for #1170, If this argument is passed in alizer devfile command then, alizer should match a devfile having the requested deployment-scope.
The issue will have to wait for #959 and #1197 as they are required for its completion (currently this value is not supported)
Accpetance Criteria
devfile
command. Also in the library.The text was updated successfully, but these errors were encountered: