Skip to content
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.

Deployment section of Getting Started guide is out of date #2915

Closed
jotaylo opened this issue Mar 7, 2023 · 1 comment · Fixed by #2921
Closed

Deployment section of Getting Started guide is out of date #2915

jotaylo opened this issue Mar 7, 2023 · 1 comment · Fixed by #2921
Assignees
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

@jotaylo
Copy link

jotaylo commented Mar 7, 2023

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

@jotaylo jotaylo added the documentation Improvements or additions to documentation label Mar 7, 2023
@AdamL-Microsoft
Copy link
Contributor

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants