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

[BUG] Backward-incompatible ARCANE_CONNECTIONSTRING secret #38

Closed
s-vitaliy opened this issue Sep 19, 2024 · 1 comment
Closed

[BUG] Backward-incompatible ARCANE_CONNECTIONSTRING secret #38

s-vitaliy opened this issue Sep 19, 2024 · 1 comment
Assignees
Labels
code/bug Something isn't working

Comments

@s-vitaliy
Copy link
Contributor

Description

The secret that contains arcane connection string should have a key named ARCANE__CONNECTIONSTRING (two underscores instead of one) for backward compatibility with old CRD layout.

Steps to reproduce the issue

  1. Create a K8S secret that does not contain ARCANE__CONNECTIONSTRING key
  2. Start a stream with this secret
  3. The stream runner fails

Describe the results you expected

The stream runner should be able to read old secrets format until SneaksAndData/arcane-operator#91 is implemented

System information

v.0.0.4, only related to a stream runner

@s-vitaliy s-vitaliy added the code/bug Something isn't working label Sep 19, 2024
@s-vitaliy s-vitaliy self-assigned this Sep 19, 2024
@s-vitaliy
Copy link
Contributor Author

Resolved with #37

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant