Skip to content

Comments

Add trigger to graphemes-api dev deployment YAML#67

Merged
ty2k merged 1 commit intodevfrom
ci/add-trigger-to-graphemes-api-deployment
May 16, 2025
Merged

Add trigger to graphemes-api dev deployment YAML#67
ty2k merged 1 commit intodevfrom
ci/add-trigger-to-graphemes-api-deployment

Conversation

@ty2k
Copy link
Collaborator

@ty2k ty2k commented May 16, 2025

Currently, the graphemes-api will not auto-deploy on new pushes to its ImageStream because of a missing trigger. This PR adds that trigger to the deployment YAML, which is already applied in the dev namespace.

@ty2k ty2k requested a review from Copilot May 16, 2025 23:51
@ty2k ty2k self-assigned this May 16, 2025
@ty2k ty2k added the cicd Continuous integration / continuous deployment pipeline label May 16, 2025
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR addresses a missing auto-deployment trigger in the graphemes-api's dev deployment YAML by adding an ImageChange trigger.

  • Added an ImageChange trigger under the triggers section.
  • Configured imageChangeParams to reference the correct ImageStreamTag.

@ty2k ty2k merged commit 6a24ec9 into dev May 16, 2025
1 check passed
@ty2k ty2k deleted the ci/add-trigger-to-graphemes-api-deployment branch May 16, 2025 23:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cicd Continuous integration / continuous deployment pipeline

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant