Skip to content
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

targets: Handle OrigUri and OrigUriApps when adding targets #442

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

detsch
Copy link
Member

@detsch detsch commented Nov 14, 2024

For custom apps targets, origUri must be set, while uri and origUriApps must be empty.
For custom ostree targets, origUriApps must be set, while uri and origUri must be empty.


@mike-sul this change seems to work, but is not enough. Apps targets generated by our CI are keeping the origUriApps field set. I'd say we need to fix the behavior there before merging this change to fioctl. Otherwise, an old origUriApps value is carried on indefinitely.

@detsch detsch requested a review from mike-sul November 14, 2024 18:43
For custom apps targets, origUri must be set, while uri and origUriApps
must be empty.
For custom ostree targets, origUriApps must be set, while uri and
origUri must be empty.

Signed-off-by: Andre Detsch <[email protected]>
@mike-sul
Copy link
Contributor

mike-sul commented Nov 15, 2024

Apps targets generated by our CI are keeping the origUriApps field set.

If by "CI" do you mean the publish job/run, then setting both uri and origUriApps to the same value (URI to the given publish run) is probably fine.

If origUriApps refers to one of the previous publish runs then this is the issue, please create a ticket and assign to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants