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

Cannot change configuration when using cloud_storage_credentials_source!=config_file #6795

Closed
nicolaferraro opened this issue Oct 17, 2022 · 1 comment · Fixed by #6864
Closed
Assignees
Labels
area/cloud-storage Shadow indexing subsystem kind/bug Something isn't working

Comments

@nicolaferraro
Copy link
Member

Version & Environment

Redpanda version: latest

What went wrong?

I started a cluster with cloud_storage_credentials_source=sts and no value for cloud_storage_access_key or cloud_storage_secret_key (they are not needed when using sts or anything different from config_file).

Trying to change another config, like cluster_id (rpk cluster config set cluster_id xxx), I get a validation error saying that both cloud_storage_access_key and cloud_storage_secret_key are required.

What should have happened instead?

When using cloud_storage_credentials_source!=config_file then cloud_storage_access_key and cloud_storage_secret_key should not be required in config validaiton

cc: @jcsp

@nicolaferraro nicolaferraro added the kind/bug Something isn't working label Oct 17, 2022
@jcsp jcsp added the area/cloud-storage Shadow indexing subsystem label Oct 17, 2022
@jcsp
Copy link
Contributor

jcsp commented Oct 17, 2022

I think this wasn't caught in tests because they set the property in extra_rp_conf before starting redpanda, and then the property is getting loaded via the bootstrap config rather than via the validated admin_server.cc path.

The validation needs fixing in admin_server.cc config_multi_property_validation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/cloud-storage Shadow indexing subsystem kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants