Skip to content
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.

fleetctl submit - name conflict #614

Closed
porjo opened this issue Jul 3, 2014 · 6 comments
Closed

fleetctl submit - name conflict #614

porjo opened this issue Jul 3, 2014 · 6 comments

Comments

@porjo
Copy link

porjo commented Jul 3, 2014

When I submit a unit file with the same name as one already in the registry, but where content differs, I get the following message:

$ fleetctl submit xxxx.service
WARNING: Job(xxxx.service) in Registry differs from local Unit(xxxx.service)

I find this message misleading. My expecation is that the unit file has been updated with the new content, however that is not the case. Running fleetctl cat xxxx.service shows the old content.

A clearer message would be:

ERROR: Job(xxxx.service) in Registry differs from local Unit(xxxx.service). No change made.

Alternatively, a 'force' flag could be added for those occasions when you really do want to overwrite the unit file. In that case the WARNING message would be appropriate.

@bcwaldon bcwaldon added this to the v0.8.1 milestone Sep 3, 2014
@bcwaldon
Copy link
Contributor

bcwaldon commented Sep 4, 2014

Related: #745

@bcwaldon bcwaldon modified the milestones: v0.8.2, v0.8.1 Sep 12, 2014
@bcwaldon bcwaldon removed this from the v0.8.4 milestone Oct 20, 2014
@jonboulle jonboulle added this to the v0.13.0 milestone Jan 25, 2016
@jonboulle
Copy link
Contributor

Let's just do a simple UX fix improvement here.

@antrik
Copy link
Contributor

antrik commented Mar 3, 2016

This UI change seems interconnected with the upcoming addition of the --replace flag (following up on #1295 and #1442 ) -- maybe it should in fact be done as part of that?

@tixxdz
Copy link
Contributor

tixxdz commented Mar 8, 2016

@antrik indeed, maybe it should just warn the user "please use --replace" ?!

@antrik
Copy link
Contributor

antrik commented Mar 9, 2016 via email

@tixxdz
Copy link
Contributor

tixxdz commented Mar 29, 2016

After #1509 is merged this one can just be fixed with this branch: https://github.com/endocode/fleet/commits/tixxdz/fleetctl-warn-user-aboutt-replace

Thanks!

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

No branches or pull requests

5 participants