feat: add support for per-deployment ROFL artifacts#698
Merged
uniyalabhishek merged 2 commits intoMay 20, 2026
Conversation
✅ Deploy Preview for oasisprotocol-cli ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
uniyalabhishek
changed the title
matevz
approved these changes
May 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
closes #697
Adds support for deployment-level artifacts in ROFL manifests, resolving effective artifacts as defaults -> global manifest artifacts -> selected deployment overrides.
This lets each deployment use its own compose file, including public deployment-specific environment config.
Tested a real Testnet ROFL build/update/deploy using a deployment-specific compose file, the deployed app served the expected deployment-specific port/content through the ROFL proxy.