-
Notifications
You must be signed in to change notification settings - Fork 184
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
Convert File Type for Files or Remote Hyperlinks in Continuous Deployment #1070
Convert File Type for Files or Remote Hyperlinks in Continuous Deployment #1070
Conversation
…ment (#1010) * First attempt at Python script to clean up extensions. * Add Python deps manifest. * Update Dockerfile with Python dependencies. * Remove additive dot before file ext and try out adding to CI harness. * Add first attempt of Python converter. * updated the tools table * Rename handler function accordingly, so docs make sense. * Fix bug with hard-coded conversion for JSON processing. * Add some more function documentation. * Complete update of function docstrings. * A little more function documentation. * Final function signature touch-ups. Co-authored-by: Michaela Iorga <michaela.iorga@nist.gov> Co-authored-by: David Waltermire <david.waltermire@nist.gov>
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.
I am Alexander Stein and I approve this message.
Jokes aside, we tested this works locally in the docker containers invoking the same scripts used by CI/CD (GitHub Actions) and verified they function as desired. Confirmed with Dave superficial YAML difference are acceptable for escaping multi-line comments and we made a best-effort attempt at get line-for-line parity.
…ment (usnistgov#1070) * Convert File Type for Files or Remote Hyperlinks in Continuous Deployment (usnistgov#1010) * First attempt at Python script to clean up extensions. * Add Python deps manifest. * Update Dockerfile with Python dependencies. * Remove additive dot before file ext and try out adding to CI harness. * Add first attempt of Python converter. * updated the tools table * Rename handler function accordingly, so docs make sense. * Fix bug with hard-coded conversion for JSON processing. * Add some more function documentation. * Complete update of function docstrings. * A little more function documentation. * Final function signature touch-ups. Co-authored-by: Michaela Iorga <michaela.iorga@nist.gov> Co-authored-by: David Waltermire <david.waltermire@nist.gov> * fix python calls to use correct python version and script Co-authored-by: Alexander Stein (Inactive) <61464190+ohsh6o@users.noreply.github.com> Co-authored-by: Michaela Iorga <michaela.iorga@nist.gov>
…ment (usnistgov#1070) * Convert File Type for Files or Remote Hyperlinks in Continuous Deployment (usnistgov#1010) * First attempt at Python script to clean up extensions. * Add Python deps manifest. * Update Dockerfile with Python dependencies. * Remove additive dot before file ext and try out adding to CI harness. * Add first attempt of Python converter. * updated the tools table * Rename handler function accordingly, so docs make sense. * Fix bug with hard-coded conversion for JSON processing. * Add some more function documentation. * Complete update of function docstrings. * A little more function documentation. * Final function signature touch-ups. Co-authored-by: Michaela Iorga <michaela.iorga@nist.gov> Co-authored-by: David Waltermire <david.waltermire@nist.gov> * fix python calls to use correct python version and script Co-authored-by: Alexander Stein (Inactive) <61464190+ohsh6o@users.noreply.github.com> Co-authored-by: Michaela Iorga <michaela.iorga@nist.gov>
Committer Notes
This PR, as part of enhancements to the current CD pipeline will fix relevant missed conversions between XML and JSON and YAML filetypes, and their respective MIME types, in place of
perl
andsed
issues. This will fix usnistgov/oscal-content#59 and GSA/fedramp-automation#129 on an ongoing basis.All Submissions:
Changes to Core Features:
Have you written new tests for your core changes, as applicable?Have you included examples of how to use your new feature(s)?Have you updated all OSCAL website and readme documentation affected by the changes you made? Changes to the OSCAL website can be made in the docs/content directory of your branch.