Model Type in backup file

[chrisch80]

Hello,

Rancid writes in the first line of the backup file the model type:

example:
!RANCID-CONTENT-TYPE: cisco-xr

Whould this also be possible somehow with Oxidized?

br
Christoph

[ytti]

I'm going to change your question.

a) Is it possible now, without touching code or model: No
b) Is it possible by touching code: Yes, I hope, obviously.

On avenue could be for example some metadata hash or array of strings, and we could have one string like 'model_name', if exists in array or hash key, output class could add it on top of every file. So all models would gain this feature, without touching models.

We could of course obviously emit that from models as well.

[robertcheramy]

Implementing this feature independently of the models seems very elegant to me.
We currently have 28 models not having a comment defined, some of them just get a config file per ftp/http/scp.
Is it acceptable in these cases to prepend the medatada with the default comment (# )?

• the user must remove it by hand when restoring a configuration.
• I don't know if we backup binary data

We could provide a method and/or variable for the models do disable metadata, so that users ca disable the feature if they don't want it.

[ytti]

We could provide a method and/or variable for the models do disable metadata, so that users ca disable the feature if they don't want it.

I'm thinking something like:

output:
  metadata:
    - model_name
    -  somethingelse

Not sure what configuration key would make most sense, and if it should be under output or main.

EDIT. Perhaps array of strings by location would be better?

output:
   metadata:
    top:
      - "!RANCID-CONTENT-TYPE: %model_name"
      -  "!DATE: %year-%month-€dayT%hour:%minute"

And is metadata most self-documenting, or is this like decorator or string.