Currently docker images are not versioned which can be an issue going further

[preetkaran20]

Is your feature request related to a problem? Please describe.
Docker images for VulnerableApp-facade just have 1 version latest. It should be the latest (whcih is unreleased) and specific tags for released versions.

For more information about the existing images: https://hub.docker.com/r/sasanlabs/owasp-vulnerableapp-facade/tags

How do we create images ?
we have a Github action for creating and pushing docker images: https://github.com/SasanLabs/VulnerableApp-facade/blob/main/.github/workflows/docker.yml

[preetkaran20]

we have used github semantic versioning in Owasp VulnerableApp project. we can use similar thing here as well.

PR: SasanLabs/VulnerableApp#382

[merry-degaga]

Karan, you can assign this to me.

I think I better understand the 'unreleased' tag. Because you want to manually create a GitHub release, by default, the most recent build/deploys will be tagged as 'unreleased'. Is this correct?

Then would you want functionality, that when someone does manually create a release, that will trigger a workflow, which can use the tag of that newly publish release and also add the 'latest' tag on DockerHub? Could this be a seperate/new issue?

Currently, with my most recent PR on the VulnerableApp repository, the latest docker build/deploy will be tagged with the version number and 'unreleased' tags.

[preetkaran20]

@merry-degaga we need the same functionality as we have in VulnerableApp repository and in both the repositories, we need an additional functionality which is to add the latest tag to docker hub and create a release as well and we will update the github release description manually with all the details.

Karan, you can assign this to me.

I think I better understand the 'unreleased' tag. Because you want to manually create a GitHub release, by default, the most recent build/deploys will be tagged as 'unreleased'. Is this correct?

Yes

Then would you want functionality, that when someone does manually create a release, that will trigger a workflow, which can use the tag of that newly publish release and also add the 'latest' tag on DockerHub? Could this be a seperate/new issue?

yes, this functionality is needed and that can be part of this ticket only.

Currently, with my most recent PR on the VulnerableApp repository, the latest docker build/deploy will be tagged with the version number and 'unreleased' tags.

yes, we need to change there as well and have a separate workflow that we will run manually for releasing the change and updating the latest tag.

[merry-degaga]

Hi Karan, is it okay to close this issue?

Thank you

[preetkaran20]

Hi Karan, is it okay to close this issue?

Thank you

@merry-degaga closed the issue and thank you!!!