-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
✨ Surface assessment tags on Archetype resource #502
Conversation
mansam
commented
Oct 3, 2023
•
edited
Loading
edited
- Use TagRefs on the Archetype resource
- Add virtual tags inherited from assessments to the Tags field on the Archetype resource
- Fixed a bug where an application would be denied membership in an archetype that wasn't a strict subset of another archetype.
Signed-off-by: Sam Lucidi <slucidi@redhat.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
api/archetype.go
Outdated
@@ -331,6 +345,7 @@ type Archetype struct { | |||
Comments string `json:"comments" yaml:"comments"` | |||
Tags []Ref `json:"tags" yaml:"tags"` | |||
CriteriaTags []Ref `json:"criteriaTags" yaml:"criteriaTags"` | |||
AssessmentTags []Ref `json:"assessmentTags" yaml:"assessmentTags"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not use TagRef for Tags
and differentiate then based on source like applications? I assume they are virtual tags?
Signed-off-by: Sam Lucidi <slucidi@redhat.com>
a5d18f9
to
1a5f19f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM