chore(quay): add Quay actions to workspace

[dzemanov]

Hey, I just made a Pull Request!

• Updates quay workspace to use @backstage-community/plugin-scaffolder-backend-module-quay

✔️ Checklist

• A changeset describing the change and affected packages. (more info)
• Added or updated documentation
• Tests for new functionality and regression tests for bug fixes
• Screenshots attached (for UI changes)
• All your commits have a Signed-off-by line in the message. (more info)

[backstage-goalie]

Changed Packages

Package Name	Package Path	Changeset Bump	Current Version
backend	workspaces/quay/packages/backend	none	v0.0.0

[karthikjeeyar]

cc: @CryptoRodeo

[CryptoRodeo]

@dzemanov LGTM, I don't see any immediate issues based on these changes. It looks like you will need to rebase though...

[CryptoRodeo]

Should this get updated too? -> https://github.com/backstage/community-plugins/blob/main/workspaces/quay/plugins/quay/src/components/QuayRepository/QuayRepository.tsx#L32

[github-actions]

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!

[dzemanov]

@CryptoRodeo pardon for replying so late. I have now rebased the PR.

Should this get updated too? -> https://github.com/backstage/community-plugins/blob/main/workspaces/quay/plugins/quay/src/components/QuayRepository/QuayRepository.tsx#L32

I would say yes. Check both quay.uiUrl and quay.apiUrl and only then fallback to no link.

[CryptoRodeo]

@dzemanov No worries

Check both quay.uiUrl and quay.apiUrl and only then fallback to no link.

Yes, that's similar to what I do here: https://github.com/backstage/community-plugins/blob/main/workspaces/quay/plugins/quay/src/api/index.ts#L76-L87

[dzemanov]

Screen.Recording.2025-03-28.at.14.40.53.mov

[CryptoRodeo]

LGTM, thanks! Someone else with more permissions will need to approve and merge this though, I still don't have full access ...

[dzemanov]

@CryptoRodeo pardon, I opened a separate PR for the other issue to keep the changes focused: #3486. Thank you for reviewing! I will ask someone to take a look.