Change upstream source from atlassian/confluence-server to atlassian/confluence

Summary

Request to update an application in Iron Bank.

Version: 9.0.1 from atlassian/confluence.

Additional Context

Our ironbank image for confluence is targeting an out of date fork of Confluence from upstream dockerhub.

the ironbank manifest

org.opencontainers.image.url: "https://hub.docker.com/r/atlassian/confluence-server"

docker/atlassian/confluence-server was last updated 6 months ago and shows that it's a legacy version of atlassian/confluence. The docker/atlassian/confluence repo clarifies that the old confluence-server has not received updates since February 2024.

This Docker image has been published as both atlassian/confluence and atlassian/confluence-server up until February 15, 2024. Both names refer to the same image. However, post-February 15, 2024, the atlassian/confluence-server version ceased receiving updates, including both existing and new tags. If you have been using atlassian/confluence-server, switch to the atlassian/confluence image to ensure access to the latest updates and new tags.

Ironbank just released a Confluence 9.0.1 build on this base image but neither of the upstream atlassian repos have a 9.0.1 build yet, and the one we are pulling from will not have one. So if we run on this image we will be using an unsupported configuration from upstream.

Can we please change the upstream target for this to the currently updated repository?

Tasks

Contributor:

• Update Dockerfile, hardening_manifest.yaml and adhere to Iron Bank requirements
• Ensure container builds successfully in the Iron Bank pipeline prior to creating an Merge Request to Development.
• Provide justifications for findings in the VAT
• Open a Merge Request from your branch to development
• Apply the StatusReview label to this issue and wait for feedback

Note: You must manually apply the StatusReview 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 Status::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 Status::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 working session every Wednesday from 1630-1730EST to answer questions.

Please read the Iron Bank Documentation for more info