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

Timestamp inserted by catalog:timestamping is not as expected #2052

Closed
skitamura7446 opened this issue Aug 14, 2024 · 0 comments · Fixed by #2114
Closed

Timestamp inserted by catalog:timestamping is not as expected #2052

skitamura7446 opened this issue Aug 14, 2024 · 0 comments · Fixed by #2114
Labels
jira kind/bug Something isn't working status/triage

Comments

@skitamura7446
Copy link

Describe the bug

The timestamp in catalog-info.yaml created by catalog:timestamping action by the backstage-scaffolder-backend-module-annotator plugin is different from the execution time of the template.
It seems that the time when the Backstage environment is deployed is probably used.

ScreenShot 437

Expected Behavior

The time indicated by backstage.io/createdAt is the time when Template was executed.

What are the steps to reproduce this bug?

  1. Deploy Red Hat Developer hub on OpenShift using the registry.redhat.io/rhdh/rhdh-hub-rhel9:1.2 image.
  2. Execute the following sample template.

Versions of software used and environment

  • Backstage(Red Hat Developer Hub): 1.2
  • OpenShift: 4.15.14
  • @janus-idp/backstage-scaffolder-backend-module-annotator: 1.0.2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira kind/bug Something isn't working status/triage
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant