Repository navigation
Migrate from @adobe/aio-cli-plugin-jwt-auth to @adobe/aio-lib-ims #129
Description
@adobe/aio-cli-plugin-jwt-auth has been deprecated in favor of @adobe/aio-lib-ims.
In order to migrate and achieve a level of backwards compatibility, there must be some migration process from the "old" configuration structure (jwt_auth) to the new one (ims.contexts.CONTEXT_NAME). This migration can be automatically done in an init hook, with the following caveats:
- If there is local config, it should be migrated to local, not global config.
- If there is global config, it should be migrated to global config.
- If the config is passed through environment variables, no migration should be done.
This will still technically be a breaking change since passphrase is not supported (see adobe/aio-lib-ims#52).
However, at this point this is blocking a separate feature request (#198) since if a flag was provided to select an alternate configuration key for the configuration used with @adobe/aio-cli-plugin-jwt-auth migration would not be possible in a fully automated fashion.
Activity
migrate to aio-lib-ims. fixes #129
migrate to aio-lib-ims. fixes #129
aiojbot commentedon Jul 9, 2020
JIRA issue created: https://jira.corp.adobe.com/browse/ACNA-847
justinedelson commentedon Sep 29, 2020
This is blocked by adobe/aio-lib-ims#52
feat(auth): replace Migrate from @adobe/aio-cli-plugin-jwt-auth to @a…
feat(auth): replace Migrate from @adobe/aio-cli-plugin-jwt-auth to @a…
feat(auth): replace Migrate from @adobe/aio-cli-plugin-jwt-auth to @a…
feat(auth): replace Migrate from @adobe/aio-cli-plugin-jwt-auth to @a…
chore(release): 1.0.0 [skip ci]
github-actions commentedon Feb 6, 2021
🎉 This issue has been resolved in version 1.0.0 🎉
The release is available on:
Your semantic-release bot 📦🚀