Support filtering deprecated devfile stacks and samples within the registry library

[kim-tsao]

/kind user-story

Which area this user story is related to?

/area registry

User Story

As a devfile client, I want to use an API to filter out deprecated devfiles so I can support only active devfiles in my tools

Acceptance Criteria

• Add support for filtering deprecated devfiles in the registry library
• Additional testing additions to account for changes done
• Additional documentation additions to Registry Library docs to describe these parameters

[UPDATE @thepetk]
This issue depends on #959

[github-actions]

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.

[michael-valdron]

related to #959

[thepetk]

We can transform 959 into an epic and include this one as child issue

[thepetk]

blocker to #1064

[thepetk]

As discussed in #959 we are not going to transform it as a child item, so I've set refinement date on 11th of August. @michael-valdron do you have any proposed workaround in mind to help us estimate the issue?

[michael-valdron]

As discussed in #959 we are not going to transform it as a child item, so I've set refinement date on 11th of August. @michael-valdron do you have any proposed workaround in mind to help us estimate the issue?

We should use similar criteria to scope this issue as with #959, I've updated the issue description to complete the acceptance criteria for this task.

[michael-valdron]

Blocked by #964

[michael-valdron]

As discussed in #959 we are not going to transform it as a child item, so I've set refinement date on 11th of August. @michael-valdron do you have any proposed workaround in mind to help us estimate the issue?

We should use similar criteria to scope this issue as with #959, I've updated the issue description to complete the acceptance criteria for this task.

It appears this issue is already part of an epic, #1063.

After reviewing and refining another child issue of the epic, #964, it appears that this will be field filtering which is covered by #959. Should we close this issue and track this as part of #959?

cc: @thepetk @kim-tsao @elsony

[michael-valdron]

As discussed in #959 we are not going to transform it as a child item, so I've set refinement date on 11th of August. @michael-valdron do you have any proposed workaround in mind to help us estimate the issue?

We should use similar criteria to scope this issue as with #959, I've updated the issue description to complete the acceptance criteria for this task.

It appears this issue is already part of an epic, #1063.

After reviewing and refining another child issue of the epic, #964, it appears that this will be field filtering which is covered by #959. Should we close this issue and track this as part of #959?

cc: @thepetk @kim-tsao @elsony

Nevermind, we can just keep "Add support for filtering deprecated devfiles in the registry library" under this issue.

[michael-valdron]

As discussed in #959 we are not going to transform it as a child item, so I've set refinement date on 11th of August. @michael-valdron do you have any proposed workaround in mind to help us estimate the issue?

We should use similar criteria to scope this issue as with #959, I've updated the issue description to complete the acceptance criteria for this task.

Revised acceptance criteria to recent refinement changes.

[michael-valdron]

Blocked by #964

Also by #959

[michael-valdron]

blocker to #1064

#959 now blocks #1064, this issue is no longer a blocker

[thepetk]

I've closed #964 as duplicate. A slight difference was that inside this issue we were explicitly mention updates to extraDevfileEntries.yaml file.

[thepetk]

Moving to next sprint as it waits for #959 to be completed

[thepetk]

No longer blocked from #959

[thepetk]

Opened PR devfile/registry-support#232 for this issue