-
Notifications
You must be signed in to change notification settings - Fork 85
[APP-14658] Fragment Imports #794
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
|
||
| message FragmentImports { | ||
| string fragment_id = 1; | ||
| string version = 2; // revision or tag |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could make this optional and just default to the latest if it is not present. But probably doesn't hurt to force the client to make it explicit.
proto/viam/app/v1/app.proto
Outdated
| optional string version = 5; // revision or tag | ||
| } | ||
|
|
||
| message FragmentImports { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably a nit, but shouldn't this be FragmentImport singular?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep! Nice catch
petrnovikov
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left one comment, otherwise LGTM!
proto, adds it as optional field to UpdateOrganizationRequest
0c9a4f6 to
ed5bd16
Compare
07601ec to
ed5bd16
Compare
Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
This PR introduces a new
FragmentImportsmessage and adds support for organization-level default fragments. Organizations can now define a list of default fragments that will be automatically applied across all machines in the organization.Changes
FragmentImports- defines fragment import configuration with support for:fragment_id- the fragment to importversion-required revision or tag to pin to a specific fragment versionprefix- optional namespace prefix to avoid resource name collisionsvariables- optional key-value pairs for fragment variable substitutionUpdateOrganizationRequest- addedrepeated FragmentImports fragment_importsfield to allow setting organization-level default fragmentsTechnical Details
Links