Business Context
A junior administrator is attempting to configure a new S3 region but is unsure about the security parameters. This scenario tests the action's robustness and error handling when faced with logically conflicting parameters (enforcing and disabling SSL simultaneously) and when a mandatory parameter is omitted.
Data Preparation
The s3.addRegion action is a server-side administrative action for configuring S3 connectivity. It does not operate on CAS tables, so no data loading is required.
Copied!
| 1 | /* No |
| 2 | data creation is necessary for this action. */ |
Étapes de réalisation
1
Attempt to add a region with conflicting SSL parameters: 'nossl=true' and 'sslrequired=true'. The action should either fail or one parameter must take precedence.
Copied!
| 1 | PROC CAS; |
| 2 | S3.addRegion / |
| 3 | name='conflict-test' |
| 4 | host='s3.test-endpoint.com' |
| 5 | region='us-west-1' |
| 6 | nossl=true |
| 7 | sslrequired=true; |
| 8 | RUN; |
2
Attempt to add a region without the mandatory 'host' parameter to verify that the action produces an error.
Copied!
| 1 | PROC CAS; |
| 2 | S3.addRegion / |
| 3 | name='no-host-test' |
| 4 | region='us-west-1'; |
| 5 | RUN; |
Expected Result
Step 1 should ideally result in an ERROR or a clear WARNING in the SAS log, stating that the SSL parameters are in conflict. If the action succeeds, the configuration of 'conflict-test' in `s3.listRegions` would reveal which parameter took precedence. Step 2 must fail with an ERROR in the log indicating that the 'host' parameter is required and was not provided.