You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a developer or system engineer using oscal-cli for development tests who wants to keep up with secure, current versions of the CLI's functionality without manually maintaining dependencies, I would like an OCI container published on Docker Hub, GitHub Container Registry (ghcr.io), and/or elsewhere for the community to use.
Goals:
a mechanism to download the CLI and dependencies all at once;
install the CLI without additional configuration or customization; and
simplify clean up for deletion, reinstallation, and use of independent copies of different versions with proper isolation and not having conflicting system configuration and dependencies
a verifiable, automation-friendly way to securely check the whole of the CLI, dependencies, and supporting data without manual verification of hashes
Dependencies:
N/A
Acceptance Criteria
All website and readme documentation affected by the changes in this issue have been updated.
A Pull Request (PR) is submitted that fully addresses the goals of this User Story. This issue is referenced in the PR.
The CI-CD build process runs without any reported errors on the PR. This can be confirmed by reviewing that all checks have passed in the PR.
The text was updated successfully, but these errors were encountered:
User Story:
As a developer or system engineer using oscal-cli for development tests who wants to keep up with secure, current versions of the CLI's functionality without manually maintaining dependencies, I would like an OCI container published on Docker Hub, GitHub Container Registry (ghcr.io), and/or elsewhere for the community to use.
Goals:
Dependencies:
N/A
Acceptance Criteria
The text was updated successfully, but these errors were encountered: