Open josefaidt opened 2 years ago
The Invalid feature flag (FF) configuration
is happening because an older version of Amplify is seeing an unknown feature flag (which has come from a newer version of CLI) and bailing. There is separate work in flight now to change how CLI handles unknown FF. That change will look at the FF and only raise an error if it is not FALSE (all new FF will be worded to be compatible with previous versions when set to FALSE). With that change, the commands listed here would work fine as long as FF is FALSE.
Keeping this issue as a feature-request to not check for FF at all on those commands.
Hi @Straubulous , is there any update on this bug fix by any chance? By mistake I opened https://github.com/aws-amplify/docs/issues/4561 in another repo, related to the exact same issue.
This bug only has made me waste hours, and I'm just one in many developers happening to use Amplify with various environments. Cannot debug a software that does not allow me to know what version it is using...
I am blocked... in a vendor lock-in spiral, it seems. The next task on my team's backlog is "transition away from AWS Amplify", unless the Amplify team is happy to fix this nonsensical bug, that causes headaches to its paying customers.
Before opening, please confirm:
How did you install the Amplify CLI?
pnpm
If applicable, what version of Node.js are you using?
v16.14.2
Amplify CLI Version
8.2.0
What operating system are you using?
mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
no
Amplify Categories
Not applicable
Amplify Commands
Not applicable
Describe the bug
Expected behavior
no feature flags checks are made and command is able to proceed
Reproduction steps
amplify init -y
amplify/cli.json
amplify version
,upgrade
, oruninstall
GraphQL schema(s)
Log output
Additional information
No response