feat: allow rock-pull-request to work with monorepo, concierge installed snaps configurable #356
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
We would like to use the
rock-pull-request.yamlworkflow to test the Temporal rocks.rock-pull-requestworkflow assumes that the github repo hosts only one rock project.rock-pull-requestinstalls a fixed set of snaps into the concierge env where the rock tests are executed. This is a limitation, as the Temporal rocks require some additional snaps installed that thejustfiletargets use.Solution
changesjob) of the form1.23.1as well astemporal-server/1.23.1. This former will ensure that observability rock repo tests continue to work, whereas the latter will ensure that the Temporal rocks monorepo is compatible with this workflow.extra-snapswhich can be used to configure the snaps installed into the concierge env. Defaults torockcraft,just,kubectlTesting
Test run in the Temporal rocks repo: https://github.com/canonical/temporal-rocks/actions/runs/15983452446/job/45131737223