Discuss Customer's Hardening Manifest Issue

Background

Ironbank contributors requested to be allowed to have a primary and secondary URL defined in the hardening_manifest's resource section. An issue describing the issue is linked here. In short, the artifacts their project utilizes will have their URLs changed, once a newer version is released. The existing version's URL is updated to an archived path, causing the CHT pipeline's import-artifacts stage to fail, as the resource's URL is no longer valid. This can require a substantial amount of time from maintainers to keep their pipeline running, and is a pain-point from a user experience perspective.

DoD

• Review the request and decide if this will be permitted
  • If this request will be accommodated, create ticket for the required pipeline update, and link that here: #379 (closed)