Comments (1)
In R1 terminology, this is getting at how to prioritize changes when using a PackageVariant or PackageVariantSet. There are three places that changes can be made:
a. In the upstream package
b. In the PackageVariant(Set) resource via a mutation using the function pipeline or injection
c. In the downstream package revision after fan out
The question comes in this flow:
- user deploy a package via a PackageVariant(Set)
- user modifies the resulting PackageRevision and publishes it
- user modifies the upstream package, and then changes the PV(S) to refer to the new revision of that upstream
- PV generates a new PackageRevision based on the updated upstream package, but the changes in the upstream package my conflict with the change made in 2)
Which should we honor, in this case? Is there a way the user should be able to control that? If so, it probably would be some policy field in PV. But if it's that, then since PVS creates PVs, how can we be selective about the ones it applies to? Should we allow that?
from nephio.
Related Issues (20)
- Remove porch code from Nephio controllers
- Add a "Porchfile" to kpt packages that stores porch-specific metadata HOT 13
- Improvement gathering on Nephio architecture
- A potential risk of porch which can be leverage to make cluster-level privilege escalation HOT 3
- Explicitly set the default value of porch's Repository object's spec.git.branch to "main" in the CRD definition
- Add one or two sentences to the release notes page (docs/release-notes/)
- Clarify which pages are draft in the documentation
- Convert TBDs to issues
- Automatic linting and language checks HOT 1
- Update porch kube code gen to use latest
- Use stock repo pkg in sandbox setup
- Investigate dropping privileged: true and explore alternatives
- Invesitage using rootless image for gitea and upgrading version to 1.20
- PackageReivsion deletionProposed sometimes deletes the packageRevision. HOT 1
- Upgrade 3pp components used in sandbox nephio install
- Update docs for OCP install
- Add WSL support for installing a Nephio management cluster
- porchctl rpkg propose/approve may fail due to a race condition as part of normal optimistic locking process
- Document the configuration parameters of the porch API server process
- dockermachines "regional" not starting HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nephio.