Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keyword replacement problem #843

Closed
6 tasks done
gregorybleiker opened this issue Aug 17, 2023 · 2 comments
Closed
6 tasks done

Keyword replacement problem #843

gregorybleiker opened this issue Aug 17, 2023 · 2 comments
Labels

Comments

@gregorybleiker
Copy link

Checklist

  • I have looked into the README and have not found a suitable solution or answer.
  • I have looked into the documentation and have not found a suitable solution or answer.
  • I have searched the issues and have not found a suitable solution or answer.
  • I have upgraded to the latest version of this tool and the issue still persists.
  • I have searched the Auth0 Community forums and have not found a suitable solution or answer.
  • I agree to the terms within the Auth0 Code of Conduct.

Description

While using v7.18.0 to export the config, with "AUTH0_PRESERVE_KEYWORDS": true,, this is not doing anything for our config atm.

We have config.js with

{
  "AUTH0_DOMAIN": "xxx",
  "AUTH0_CLIENT_ID": "xxx",
  "AUTH0_CLIENT_SECRET": "xxx",
  "AUTH0_KEYWORD_REPLACE_MAPPINGS": {
    "AUDIENCE_GRAPHQL_TEST": "bla.bla.bla",
    ...

and tenant.yaml with

  - name: GraphQL Test
    identifier: ##AUDIENCE_GRAPHQL_TEST##

but on export this keyword gets overriden with bla.bla.bla. Is there any way to debug the replacement? Our real config.js and tenant.yaml are much larger in reality, but I don't want to redact all values.

Expectation

Keywords are preserved

Reproduction

Seeing this seems to be only the case with our config, this cannot be reproduced without our tenant login. The command we run is: a0deploy.cmd export --output_folder .\DEV --format yaml -c .\configs\config_dev.json

Deploy CLI version

7.18.0

Node version

18.17.0

@willvedd
Copy link
Contributor

@gregorybleiker Can you provide more information here? Your issues suggests that keyword preservation doesn't work at all but I can assure you that it does for a wide-array of resources. Admittedly, there are some blindspots, see: #855 . However, it would be useful to see more of your configuration so I can replicate the specific issue.

@willvedd
Copy link
Contributor

willvedd commented Nov 21, 2023

Thanks for opening this issue. I'm going to close this out because I'm unable to troubleshoot with the provided information. It is also possible that its a duplicate of #845 or #855. Please feel empowered to open a new ticket if you ned further assistance!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants