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

When selecting Vault as a service, generated config file fails validation #217

Open
gilzow opened this issue Apr 15, 2024 · 0 comments
Open

Comments

@gilzow
Copy link
Contributor

gilzow commented Apr 15, 2024

If you select Vault duing the {paas} ify process, the generated configuration file fails validation (during push) with the message:

  E: Error parsing configuration files:
      - services: Uncaught exception: Vault service requires explicit endpoint configuration.
          at <script>:2:4
                throw(

My guess is that it is difficult, if not impossible, to know what a user needs for keys and types in their endpoint configuration, but we should then warn them that because they've selected Vault as a service they'll be required to add the endpoint configuration and then link to the docs.

@akalipetis akalipetis added the Platformify label Jul 2, 2024 — with Linear
@linear linear bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 2, 2025
@akalipetis akalipetis reopened this Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants