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 Nov 1, 2023. It is now read-only.
The deployment steps don't give any guidance on how to generate the client_id code for the config file.
I was able to get a deployment set up in release 6.3.0 by adding the --auto_create_cli_app flag to the deploy.py arguments, but with the refactoring for the config file for 6.4.0 the same command fails with:
"Exception: CLI client_id not provided as valid key. Please Provide Valid Config."
The documentation might need to be updated to clear up confusion on this, but I think that the behavior you see here is unexpected, and this is actually a bug in the config refactoring.
The intention is that you should be able to start a new deploy while passing the --auto_create_cli_app flag while using a config file that doesn't already have the not-yet-created CLI app ID key + value.
The deployment steps don't give any guidance on how to generate the client_id code for the config file.
I was able to get a deployment set up in release 6.3.0 by adding the --auto_create_cli_app flag to the deploy.py arguments, but with the refactoring for the config file for 6.4.0 the same command fails with:
"Exception: CLI client_id not provided as valid key. Please Provide Valid Config."
AB#36144
The text was updated successfully, but these errors were encountered: