-
Notifications
You must be signed in to change notification settings - Fork 61
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
feat: add inheritance view to ssp-generate and ssp-assemble #1441
Conversation
…component Adds ExportInterface and ExportWriter classes Adds Markdown generation to ssp-generate Add MarkdownWriter for leveraged statements Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com> Signed-off-by: Alex Flom <alexander.flom@gmail.com>
…markdown Adds InheritanceMarkdownReader for processing into a leveraging SSP context Adds persistance for components and satisified statements during updates Changes leveraging component from a single dictionary to a list Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com>
Adds ExportReader class Removes ExportInterface class Adds a single ByComponentInterface class to interact with the model in terms of inheritance Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com> Co-authored-by: Jennifer Power <barnabei.jennifer@gmail.com>
… inheritance Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com>
Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com>
Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com>
…ader Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com>
…ve regex Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com>
Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com>
Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com>
…aged_ssp Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com>
Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com>
…eritance view Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com>
Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com>
Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com>
Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com>
Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com>
Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com>
Adds SSPInheritanceAPI class for interacting with leveraged auth information Adds trestle global tags to markdown to store SSP location info Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com> Co-authored-by: Alex Flom <alexander.flom@gmail.com>
Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com>
@AleJo2995 @vikas-agarwal76 Added you both as reviewers to get your thoughts on this approach. We added enough here to address the two linked issues and get to the point where we can complete additional testing, so the scope of this feature should not increase. Thanks in advance! |
Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com>
Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com>
Perhaps these pre-existed, but sonar says there are 3 code smells https://sonarcloud.io/project/issues?resolved=false&types=CODE_SMELL&sinceLeakPeriod=true&pullRequest=1441&id=compliance-trestle Not essential that these get fixed, but it would be nice... |
@@ -519,10 +563,18 @@ def _run(self, args: argparse.Namespace) -> int: | |||
raise TrestleError('Original ssp has no system component.') | |||
comp_dict[const.SSP_MAIN_COMP_NAME] = sys_comp | |||
|
|||
ssp_sys_imp_comps = ssp.system_implementation.components |
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.
@vikas-agarwal76 Just wanted to call out this logic specifically. This is really the only change to ssp-assemble
that was made that could affect the current workflow. Though it would only apply to a leveraging SSP. All other changes are processed conditionally when the leveraged-ssp
flag is used (generate
) or the inheritance markdown is present (assemble
).
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.
Small changes.
docs/tutorials/ssp_profile_catalog_authoring/ssp_profile_catalog_authoring.md
Outdated
Show resolved
Hide resolved
docs/tutorials/ssp_profile_catalog_authoring/ssp_profile_catalog_authoring.md
Outdated
Show resolved
Hide resolved
Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com>
Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com>
@degenaro Working through these. I believe only one was pre-existing. |
@vikas-agarwal76 Changes addressing your feedback added on this commit - a10ba54. Please let me know if there are any additional changes or feedback. |
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
Thanks @vikas-agarwal76. Just wanted to confirm with you, @AleJo2995, and @degenaro, are there any other actions that need to be taken before merge? Thanks in advance! |
Types of changes
Quality assurance (all should be covered).
Summary
Adds an inheritance view to the generated trestle markdown that allows exported provided and responsibility statements to from a leveraged SSP to be used.
Closes #1398
Closes #1393
ssp-generate
ssp-assemble
Assumptions/Constraints
control implementation
of the SSP and edits the existing implemented requirements. It will edit or add by-component assemblies with the information.responsibility
uuid can only occur once in thesatisfied
array and theprovided
uuid can only occur once in theinherited
array.leveraged authorization
section will not be present)What this does not do
Key links:
Before you merge