Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
  • Loading branch information
adejanovski authored Jun 14, 2024
1 parent decc739 commit 51316ee
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion docs/Configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ region = <Region hosting the storage>
; If not specified, we default to the 'hottest' class (STANDARD, STANDARD, HOT for GCP, AWS, AZURE respectively).
; Supported values:
; AWS S3: STANDARD | REDUCED_REDUNDANCY | STANDARD_IA | ONEZONE_IA | INTELLIGENT_TIERING
; GCP: STANDARD | NEARLINE | COLDLINE | ARCHIVE
; GCP: STANDARD | Unsupported | Unsupported | Unsupported
; AZURE: HOT | COOL | COLD
; https://aws.amazon.com/s3/storage-classes/
; https://cloud.google.com/storage/docs/storage-classes
Expand Down
2 changes: 1 addition & 1 deletion medusa-example.ini
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,7 @@ storage_provider = <Storage system used for backups>
; If not specified, we default to the 'hottest' class (STANDARD, STANDARD, HOT for GCP, AWS, AZURE respectively).
; Supported values:
; AWS S3: STANDARD | REDUCED_REDUNDANCY | STANDARD_IA | ONEZONE_IA | INTELLIGENT_TIERING
; GCP: STANDARD | NEARLINE | COLDLINE | ARCHIVE
; GCP: STANDARD | Unsupported | Unsupported | Unsupported
; AZURE: HOT | COOL | COLD
; https://aws.amazon.com/s3/storage-classes/
; https://cloud.google.com/storage/docs/storage-classes
Expand Down
2 changes: 1 addition & 1 deletion tests/integration/features/integration_tests.feature
Original file line number Diff line number Diff line change
Expand Up @@ -1148,7 +1148,7 @@ Feature: Integration tests
| local | with_client_encryption |

@32
Scenario Outline: Perform an differential backup with explicit storage class, then verify it
Scenario Outline: Perform a differential backup with explicit storage class, then verify it
Given I have a fresh ccm cluster "<client encryption>" running named "scenario32"
Given I will use "<storage class>" as storage class in the storage
Given I am using "<storage>" as storage provider in ccm cluster "<client encryption>" with gRPC server
Expand Down

0 comments on commit 51316ee

Please sign in to comment.