Openpages internally addresses content via object UUIDs
Approach:
Given an OSCAL object (e.g. a profile) and a desired Openpages host (+ credentials over http basic auth)
trestle task must first:
1) Build the assembly of OSCAL objects together.
2) For each of the dependencies from catalogs up check whether those dependencies are in openpages - this is to be done via the href structure (e.g. is it pointing to the provided host name?)
3) If not upload the content capturing the UUID it is stored in and log.
4) rewrite upstream objects referring to the object now in openpages.
5) Upload those new objects.
Example cli
trestle tasks oscal-upload --file my_profile.json --host https://my_open_pages_host.com
Issue description / feature objectives
Assumptions:
Approach: Given an OSCAL object (e.g. a profile) and a desired Openpages host (+ credentials over http basic auth)
trestle task must first: 1) Build the assembly of OSCAL objects together. 2) For each of the dependencies from catalogs up check whether those dependencies are in openpages - this is to be done via the href structure (e.g. is it pointing to the provided host name?) 3) If not upload the content capturing the UUID it is stored in and log. 4) rewrite upstream objects referring to the object now in openpages. 5) Upload those new objects.
Example cli
trestle tasks oscal-upload --file my_profile.json --host https://my_open_pages_host.com
example href from profile