Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deploy_timestamp should include image registry URL so that users can verify the source of the deployment information #1090

Open
1 task done
etsauer opened this issue Oct 18, 2023 · 0 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@etsauer
Copy link
Collaborator

etsauer commented Oct 18, 2023

Feature description

Currently deploy_timestamp looks like this:

deploy_timestamp{app="/pelorus-api/", image_sha="sha256:224670e8fa597b2aa5c6bb242e5d5c69522a73dcf4a364c59e85b9e55b8545e5"}

I would like to modify it to also include the pull URL for the image so that users can go and validate where we are getting the data from.

Like so:

deploy_timestamp{app="/pelorus-api/", image_sha="sha256:224670e8fa597b2aa5c6bb242e5d5c69522a73dcf4a364c59e85b9e55b8545e5", image_url="https://quay.io/repository/etsauer/quarkus-app/manifest/sha256:224670e8fa597b2aa5c6bb242e5d5c69522a73dcf4a364c59e85b9e55b8545e5"}

How this will help you

This is greatly improve our data quality and integrity, and help users understand whats going on under the hood of pelorus

Feature priority

⌛ It will greatly improve my experience using Pelorus

Code of Conduct

  • I agree to follow Pelorus's Code of Conduct
@etsauer etsauer added kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

1 participant