Allow Twined service containers from public repositories to be deployed to Twined service networks #740
Description
Feature request
Use Case
We should be able to use public containers (containers built from code in public GitHub repositories) in private Twined service networks, or at the very least allow pushing of containers to service networks without the GitHub account being tied to the network.
Current state
Service code/containers have to be deployed from the same GitHub account as is tied to the Twined service network
Proposed Solution
A different constraint applied to workload identity federation needs to be applied (it's currently that any GitHub Actions workflows are run from a specific GitHub account, limiting pushing of images to the artifact registry)