Issue going from the legacy Pex to Pex v2
fierceeo opened this issue · 3 comments
Hi, I am having an issue when going from the legacy Pex to Pex v2. There is an issue with the conversion and I am getting the file "permissions.yml.legacy-backup" instead of permissions.yml.
Thanks,
Ram
PEX 2 doesn't use permissions.yml - when you update, it should migrate to whichever backend is specified in the config, which is by default permissions.json (which you have, according to
an earlier version of your message).
That's not entirely true -- the schema migration and the file type migration are separate -- but both are automatically performed when loading the file backend. This means that you could theoretically write a yaml file with the v2 schema, or a json file with the v1 schema, and PEX should be able to load either just fine :)
…On Thu, Feb 27, 2020, at 08:21, md678685 wrote:
PEX 2 doesn't use `permissions.yml` - when you update, it should migrate to whichever backend is specified in the config, which is by default `permissions.json` (which you have, according to
an earlier version of your message <https://user-images.githubusercontent.com/1917406/75462971-02253b80-597d-11ea-8b26-84371ac41078.jpg>).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#3078?email_source=notifications&email_token=AAEZSZHIBIJ3N7M2OAEWDSLRE7R7JA5CNFSM4K4TTQX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENE6VKQ#issuecomment-592046762>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEZSZGLAMFK6JHNNLGCXADRE7R7JANCNFSM4K4TTQXQ>.
As of 9e4e11b this issue should be fixed.