You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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?
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:
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:
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.
The text was updated successfully, but these errors were encountered: