Major: Allow setting the s3 secret keys #15

Merged

jessebot merged 1 commit from allow-setting-s3-keys into main

2026-08-17 12:29:40 +00:00

jessebot commented

2026-08-17 12:28:45 +00:00

Owner

This changes gotosocial.config.storage.s3.existingSecret to gotosocial.config.storage.s3.existingSecretName to match the other existingSecret values we have throughout the file and accommodate setting the name of the S3 access and secret keys. The new configuration is as follows:

gotosocial:
  config:
    storage:
      s3:
        # -- If this is set, accessKey, secretKey will not be used
	    existingSecretName: ""
	    existingSecretKeys:
	      # -- Access key part of the S3 credentials. This can be changed to anything you like.
	      accessKey: "S3_ACCESS_KEY_ID"
	      # -- Secret key part of the S3 credentials. This can be changed to anything you like.
          secretKey: "S3_SECRET_ACCESS_KEY"

This changes `gotosocial.config.storage.s3.existingSecret` to `gotosocial.config.storage.s3.existingSecretName` to match the other existingSecret values we have throughout the file and accommodate setting the name of the S3 access and secret keys. The new configuration is as follows: ```yaml gotosocial: config: storage: s3: # -- If this is set, accessKey, secretKey will not be used existingSecretName: "" existingSecretKeys: # -- Access key part of the S3 credentials. This can be changed to anything you like. accessKey: "S3_ACCESS_KEY_ID" # -- Secret key part of the S3 credentials. This can be changed to anything you like. secretKey: "S3_SECRET_ACCESS_KEY" ```

jessebot added the

major

label

2026-08-17 12:28:45 +00:00

jessebot self-assigned this

2026-08-17 12:28:45 +00:00

jessebot added 1 commit

2026-08-17 12:28:45 +00:00

allow setting the s3 secret keys

Helm Lint / lint (pull_request) Failing after 5s

Details

Bump Semver / check-labels (pull_request) Successful in 1s