I may be misunderstanding this, and if using override.ts, there's another way of acccessing the values that are set, instead of using aws-exports.js, but I'm not sure what this process is if it exists.
Thanks!
Before submitting, please confirm:
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v16.20.2
Amplify CLI Version
12.12.6
What operating system are you using?
macOS
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
N/A
Describe the bug
When setting OAuth values in
amplify/backend/auth/<app>/override.ts
, for example:These values are not added to the
aws-exports.js
file.If the values are added to
cli-inputs.json
, for example:The values do appear in
aws-exports.js
:My understanding is these should be equivalent and
override.ts
is the more modern way of adding these settings.Expected behavior
aws-exports.js contains OAuth values when set from
override.ts
fileReproduction steps
amplify/backend/auth/<app>/override.ts
to add OAuth properties a. e.g.amplify push
aws-exports.js
does not updateProject Identifier
No response
Log output
No response
Additional information
I may be misunderstanding this, and if using
override.ts
, there's another way of acccessing the values that are set, instead of usingaws-exports.js
, but I'm not sure what this process is if it exists.Thanks!
Before submitting, please confirm: