UNCLASSIFIED - NO CUI

Skip to content

Merge updateBaseAndMaintainers into Development

Summary

    Request to update an application in Iron Bank.

    Version: (State the version you would like the application updated to)

    ## Tasks

    Contributor:
    - [x] Update `Dockerfile`, `hardening_manifest.yaml` and adhere to Iron Bank [requirements](https://docs-ironbank.dso.mil/hardening/overview/)
    - [x] Ensure container builds successfully in the Iron Bank pipeline prior to creating an Merge Request to `Development`.
    - [X] Provide justifications for findings in the [VAT](https://vat.dso.mil)
    - [x] Open a Merge Request from your branch to `development`
    - [x] Apply the ~"Hardening::Review" label to this issue and wait for feedback
    ###### ***Note: You must manually apply the ~"Hardening::Review" label in order to have a CHT member review your merge request.***

    Iron Bank:
    - [ ] Merge contributor branch to `development`
    - [ ] Review findings and justifications
    - [ ] Merge `development` to `master` and close issue

    > Note: If the above process is rejected for any reason, the `Hardening::Verification` label will be removed and the issue will be sent back to `Open`. Any comments will be listed in this issue for you to address. Once they have been addressed, you **must** re-add the `Hardening::Verification` label.

    ## Questions?

    Contact the Iron Bank team by commenting on this issue with your questions or concerns. If you do not receive a response, add `/cc @ironbank-notifications/onboarding`.

    Additionally, Iron Bank hosts an [AMA](https://www.zoomgov.com/meeting/register/vJIsf-ytpz8qHSN_JW8Hl9Qf0AZZXSCSmfo) working session every Wednesday from 1630-1730EST to answer questions.

    Please read the [Iron Bank Documentation](https://docs-ironbank.dso.mil/) for more info

    /label ~"Container::Update"
Edited by Kevin Moy
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information