vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If neither is specified the bucket's DefaultRetention period will be used. Zero (0) is a legal value assuming the bucket's minimum retention period is also 0. 
 Retention-expiration-date Date (ISO 8601 Format) Date on which it is legal to delete or modify the object. You can only specify this or the Retention-Period header. If both are specified a 400 error will be returned. If neither is specified the bucket's DefaultRetention period will be used. Supported ISO 8601 format is [YYYY]-[MM]-[DD]T[hh]:[mm]:[ss]Z or [YYYY][DD]T[hh][ss]Z (for example, 2020-11-28T03:10:01Z or 20201128T031001Z are both valid). 
 Retention-legal-hold-id String A single legal hold to apply to the object. A legal hold is a Y character long string. The object cannot be overwritten or deleted until all legal holds associated with the object are removed. 





* Java
* Python
* Node



public static void putObjectAddLegalHold(String bucketName, String objectName, String fileText, String legalHoldId) {
System.out.printf("Add legal hold %s to %s in bucket %s with a putObject operation.n", legalHoldId, objectName, bucketName);

InputStream newStream = new ByteArrayInputStream(fileText.getBytes(StandardCharsets.UTF_8));

ObjectMetadata metadata = new ObjectMetadata();
metadata.setContentLength(fileText.length());

PutObjectRequest req = new PutObjectRequest(
bucketName,
objectName,
newStream,
metadata
);
req.setRetentionLegalHoldId(legalHoldId);

cos.putObject(req);
Prefix String None Filter The rule applies to any objects with keys that match this prefix. 
 Expiration Container Days or Date Rule Limit 1. 
 Days Non-negative integer None Expiration Must be a value greater than 0. 
 Date Date None Expiration Must be in ISO 8601 Format. 
 NoncurrentVersionExpiration Date NoncurrentDays Rule Limit 1. 
 NoncurrentDays Non-negative integer None NoncurrentVersionExpiration Must be a value greater than 0. 



The body of the request must contain an XML block with the schema that is addressed in the table (see Example 1).

<LifecycleConfiguration>
<Rule>
<ID>id1</ID>
<Filter />
<Status>Enabled</Status>
<Expiration>
<Days>60</Days>
</Expiration>
</Rule>
</LifecycleConfiguration>

Syntax

PUT https://{endpoint}/{bucket}?lifecycle path style
PUT https://{bucket}.{endpoint}?lifecycle virtual host style

Example request

PUT /images?lifecycle HTTP/1.1
Host: s3.us.cloud-object-storage.appdomain.cloud
Date: Wed, 7 Feb 2018 17:50:00 GMT
Authorization: authorization string
Content-Type: text/plain
Content-MD5: M625BaNwd/OytcM7O5gIaQ==
Content-Length: 305

<LifecycleConfiguration>
<Rule>
<ID>id1</ID>
<Filter />
<Status>Enabled</Status>
<Expiration>
<Days>60</Days>
</Expiration>
</Rule>
</LifecycleConfiguration>
Show more

Code sample for use with NodeJS COS SDK

Using the IBM Cloud® Object Storage SDKs only requires calling the appropriate functions with the correct parameters and proper configuration.

var aws = require('ibm-cos-sdk');
For more information, see [Automatically rotating your secrets](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-automatic-rotation).
2. Schedule automatic rotation to take place before your secrets are set to expire.

To avoid interruptions to your applications, it's recommended that you set the minimum interval between automatic rotation and expiration date to 30 days.







 Avoid application outages by locking your secrets 

Use locks to plan for periodic rotation of secrets. When you create and remove locks on a secret as part of an automated workflow, you can safely delete secrets only after their newest versions are fully deployed to your applications.



1. Create locks on a secret to represent the applications or services that use it. To create a lock from the Secrets Manager UI, go to Secrets page and click the Actions menu ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/991f60ddbe3ab0a9aa69481a07a0a73b359fa329/icons/actions-icon-vertical.svg)> Locks.

You can think of a lock as a kind of mapping that you can create between a secret and the client or application that consumes it. If a secret has a lock attached to it, it means that shouldn't be modified because it's currently in use by your application.

A secret can be unlocked and able to be deleted or modified only after all of its associated locks are removed.
2. Build an automated flow that can help you to safely delete old or expired secrets from your instance only after your applications have picked up the latest secret versions. For example, consider the following scenario:

You create a secret that expires in 89 days and is scheduled to be automatically rotated in 90 days.



Table 1. Example automated workflow for locking secrets.

 Description of action 

 1 Run an pipeline that obtains the secret from Secrets Manager and deploys it to a Kubernetes cluster so that it can be used by your applications. 
 2 Create locks on the current version of the secret (one lock to for each application or service that uses the secret).
For more information about creating and storing IAM credentials, see [Creating IAM credentials](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-iam-credentials).





 What happens when I rotate my secret? 

When a secret is rotated, a new version of its value becomes available for use. You can choose to manually add a value or automatically generate one at regular intervals by enabling automatic rotation.

For more information about secret rotation, see [Rotating secrets](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-manual-rotation).





 What happens when my secret expires? 

In some secret types such as arbitrary or username_password, you can set the date and time when your secret expires. When the secret reaches its expiration date, it transitions to a Destroyed state. When the transition happens, the value that is associated with the secret is no longer recoverable. The transition to the Destroyed state can take up to a couple of minutes after the secret expires, or a lock that prevented expiration is removed.

For more information about how your information is protected, see [Securing your data](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-mng-data).





 What are differences between the Reader and SecretsReader roles? 

Both the Reader and SecretsReader roles help you to assign read-only access to Secrets Manager resources.



* As a reader, you can browse a high-level view of secrets in your instance. Readers can't access the payload of a secret.
* As a secrets reader, you can browse a high-level view of secrets, and you can access the payload of a secret. A secrets reader can't create secrets or modify the value of an existing secret.







 How is Secrets Manager different from Key Protect? 

There are a few key differences between using Key Protect and Secrets Manager to store your sensitive data. Secrets Manager offers flexibility with the types of secrets that you can create and lease to applications and services on-demand. Whereas, Key Protect delivers on encryption keys that are rooted in FIPS 140-2 Level 3
id=reclamation_id,
action_name='restore'
).get_result()

print('nrun_reclamation_action() response:n',
json.dumps(reclamation, indent=2))

runReclamationActionOptions := resourceControllerService.NewRunReclamationActionOptions(
reclamationID,
"restore",
)

reclamation, response, err := resourceControllerService.RunReclamationAction(runReclamationActionOptions)
if err != nil {
panic(err)
}
b, _ := json.MarshalIndent(reclamation, "", " ")
fmt.Printf("nRunReclamationAction() response:n%sn", string(b))

const params = {
id: reclamationId,
actionName: 'restore',
};

resourceControllerService.runReclamationAction(params)
.then(res => {
console.log('runReclamationAction() response:n' + JSON.stringify(res.result, null, 2));
})
.catch(err => {
console.warn(err)
});
panic(err)
}

const params = {
accountId: accountId,
iamId: deleteUserId,
};

userManagementAdminService.removeUser(params)
.then(res => {
console.log(JSON.stringify(res.result, null, 2));
})
.catch(err => {
console.warn(err)
});
[Automatic renewal](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-auto-renewal) is attempted 30 days before expiration. <br> <br>If automatic renewal fails, [manually update the peer certificates](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-enroll-tls-peer). Production outage <br> <br>SDK does not allow connection when TLS certificates are expired. [Manually update the peer certificates](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-enroll-tls-peer). 







 Orderer certificates 



Table 3. How to manage the orderer certificates

 Certificate Description How generated Default expiration How to view expiration How to renew Impact if expires What to do if expired 

 Orderer enrollment certificate (signcert) The public key that the orderer uses to sign transactions. Generated when the ordering node is deployed based on the ordering service enroll ID and secret that is provided. 1 year Open console ordering node and view Enrollment Cert Expiration field. [Automatic renewal](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-auto-renewal) is attempted 30 days before expiration. <br> <br>If automatic renewal fails, see [Manual certificate renewal](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-enroll-tls-ordering-node) Production outage <br> <br>Orderers can no longer work. [Manual certificate renewal](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-enroll-tls-ordering-node)
,
"reasons":
{
"code": "KEY_ACTION_INVALID_STATE_ERR",
"message": "Key is not in a valid state",
"status": 409,
"moreInfo": "https://cloud.ibm.com/apidocs/key-protect"
}
]
}
]
}







 Example 2 

The key disable request fails because the key has expired and you are attempting to change the key state from disabled (state value is 3) to enabled (state value is 1).

The following steps return a key has been disabled error.



1. Create a key with an expiration date
2. Allow the expiration date to pass
3. Enable the key



 on a Mac, add 1 (one) minute to the current time
$ EXPIRE=$(date -u -v+1M "+%Y-%m-%dT%H:%M:%SZ")

$ echo $EXPIRE

 step 1 - create a key with an expiration date
$ curl -X POST "https://us-south.kms.cloud.ibm.com/api/v2/keys" -H "authorization: Bearer $ACCESS_TOKEN" -H "bluemix-instance: $KP_INSTANCE_ID" -H "content-type: application/vnd.ibm.kms.key+json" -d '{
"metadata": {
"collectionType": "application/vnd.ibm.kms.key+json",
"collectionTotal": 1
},
"resources": [
{
"type": "application/vnd.ibm.kms.key+json",
"name": "Root-key-1",
"description": "example-key",
"expirationDate": "'$EXPIRE'",
"extractable": false
}
]
}'
Show more



 JSON response 

{
"metadata": {
Suspending a version of a private product 

If you need to remove a version of your software that's published to your account without permanently deleting or deprecating it, you can suspend it for 7 days. Suspending a product can be useful if, for example, you discover a bug or a vulnerability in your product that must be investigated before more users install it.

Suspending a version of your product will not permanently delete it from your account. If you need to permanently delete a version of your product, deprecate it instead.

Complete the following steps to suspend your version:



1.  In the IBM Cloud console, click Manage > Catalogs > Private catalogs.
2.  Select the private catalog where your product is located.
3.  Select your product.
4.  Select the version that you want to suspend.

If your software has only one shared version, and you suspend that version, the entire product is suspended.
5.  Open the Actions menu and select Suspend.
6.  Click Suspend.



You can also suspend a version by clicking the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/actions-icon-vertical.svg) for that version and selecting Suspend.

After you suspend a version of your product, you must share it again within 7 days, or your version will be deprecated. Deprecated versions are removed after 90 days. For more information, see [Sharing private catalog products](https://cloud.ibm.com/docs/account?topic=account-catalog-share&interface=ui).

IBM Cloud can suspend your product if there's an issue that you need to address. Any updates that you need to make are shared by email.
Why am I disconnected from VPN after a period of time? 

SSL VPN will auto-disconnect if a user becomes idle.

  Why it’s happening 

User is disconnected if idle for a period of time, since this is not a dedicated VPN it does have a few limitations.

  How to fix it 

Auto-disconnect is working as expected because SSL VPN is designed to manage classic servers, and is not for production use. There is a check against idle clients and the token is terminated if time is up.
For example, if you cancel an hourly instance after 10 days, you pay for only the hours for those 10 days. If you cancel a monthly instance after 10 days, you pay for the whole month. If you're interested in the suspend billing feature, which is only available on hourly instances, see [About suspend billing](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-requirements). 
 Hostname Can contain labels that are made of alphanumeric characters and dashes, which are separated by periods. Labels cannot be numeric only, begin or end with a dash, nor have consecutive dashes or periods. 
 Domain Must have two or more labels that can be made of alphanumeric characters and dashes, which are separated by periods. Labels can't begin or end with a dash, or have consecutive dashes or periods. The last label must be letters only. 
 Placement group You can select a placement group for your instance. If you add a placement group, the "spread" rule means that the instances are on different physical hardware. For more information, see [Placement groups](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-placement-groups). 
 Location Locations are composed of regions (specific geographic areas) and zones (fault tolerant data centers within a region). Select the location where you want your virtual server instance to be created. 
 Popular profiles Consider selecting from popular profile configurations that support most common use cases. Profiles contain preconfigured instances that are ready to use in a matter of minutes. 
 All profiles For more information about available profile options for public instances, see [Public virtual servers](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-about-public-virtual-servers). 
 SSH keys SSH keys allow access to an instance without using a password from corresponding clients for each public key that is implemented on the instance. If you decide to add an SSH key, provide a public key of your SSH key, which you can use to log in to your instance after it is provisioned. 
 Image An image is the deployed operating system for your instance.
| | subject | The user account that activated the item. | | activationId | ID of this activation record. | | start | Time when the activation began. | | end | Time when the activation completed. | | duration | Time, in milliseconds, that it took for the activation to complete. | | response | - status: The exit status of the activation. \n - statusCode: The status code. If the action resulted in an error, this value is the HTTP error code. \n - success: The result of whether the action completed successfully. \n - result: The return value from the activation. \n For more possible outcomes, see [Action executions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-limitslimits_exec). | | logs | Logs for this activation. | | annotations | Annotations on this action. For a list of possible activation annotations, see the [annotations reference topic](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-annotationsannotations_activation). | | publish | The result of whether the action is published. |





 Viewing logs in IBM Log Analysis 

Action logs are forwarded to an IBM Log Analysis service where they are indexed, enabling full-text search through all generated messages and convenient querying based on specific fields.

To get started, complete the following steps.



1. Navigate to the IBM Log Analysis service and create an instance in the same region as your Cloud Functions namespace.
2. Configure the Log Analysis instance to receive platform service logs.



You can also launch logging from your Cloud Functions dashboard by selecting Launch Logging.



 Configure IBM Log Analysis 

To use the [IBM Log Analysis service](https://cloud.ibm.com/observe/logging) to view the logs of your Cloud Functions actions, you need to provision an instance first.
The readiness check has not run recently enough to reflect accurate results. Run a new check to see the current status. Readiness checks expire 5 hours after they complete.





 Ready 

Your vSRX is ready to perform the given action.





 Not Ready 

Your vSRX is not ready to perform the action in question. This could occur because of several reasons. Either a readiness check error occurred, or the readiness check did not complete fast enough, and timed out.

Error messages for the issues found during the readiness check display next to the module. Click on the error codes to get more information on each error. Alternatively, you can find information about each error in the topic [Understanding readiness errors](https://cloud.ibm.com/docs/vsrx?topic=vsrx-readiness-errors).





 Running 

The readiness check is currently running on your vSRX, and has not currently encountered any errors.





 Incomplete 

The first member of the gateway's highly available (HA) setup failed the readiness check. As a result, the gateway could not complete the readiness check.





 Unsupported 

The action you are attempting to check is not supported for this gateway.





 Current 

The action you are attempting to check does not need to be performed, as the gateway already has the latest version available.
As an example, let's say that you're creating a conditional policy for a developer that is based in Dublin. In this case, select UTC+1 so that the date and time range that you select in the next step enforces access at the right time for that location.



1. Complete the fields for the date and time range that that determines when the condition grants and terminates access.
2. Click Create.
3. Click Review.
4. Click Add to add your policy configuration to your policy summary.
5. Click Assign.



Temporary policies aren't automatically removed. To avoid reaching the policy limit in the account, administrators can remove the policy manually after it expires.

For more information about time-based conditions for access policies, see [Conditions in access policies](https://cloud.ibm.com/docs/account?topic=account-iam-condition-properties&interface=uipolicy-condition-properties).





 Creating a temporary time-based condition by using the CLI 

You can assign access for a finite duration by specifying a date and time range that determines when the condition grants and terminates access. For example, you might have a user that needs to present a demonstration on your account for a few hours or a contractor that needs temporary access to a service over a couple days.

The following example shows you how to create a one-time time-based condition for you account by granting the user temporary access as an Operator for all Account Management Services.



1. Log in to IBM Cloud® CLI. If you have multiple accounts, you are prompted to select which account to use. If you do not specify a region with the -r flag, you must also select a region.

ibmcloud login

If your credentials are rejected, you might be using a federated ID. To log in with a federated ID, use the --sso flag. See [Logging in with a federated ID](https://cloud.ibm.com/docs/account?topic=account-federated_id) for more details.
You will add a second conditional response to the Not found section that checks whether the counter is greater than 1, which indicates that the user has provided an invalid response 3 times previously. In this case, the dialog assigns the time value on the user's behalf to the popular dinner reservation time of 8 PM. Don't worry; the user will have a chance to change the time value when the confirmation slot is triggered. Click Add a response.
11. Add the following condition and response.



Not found response details

 Condition Response 

 `$counter > 1` You seem to be having trouble choosing a time. I will make the reservation at 8PM for you. 



You must set the $time variable to 8PM, so click the Edit response![Edit response](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/edit-slot.png) icon. Select Open JSON editor, add the following context variable definition, and then click Back.

{
"output": {
"text": {
"values": [
"You seem to be having trouble choosing a time.
I will make the reservation at 8 PM for you."
]
}
},
"context": {
"time": "<? '20:00:00'.reformatDateTime('h:mm a') ?>"
}
}
12. The conditional response that you just added has a more precise condition than the true condition that is used by the first conditional response. You must move this response so it comes before the original conditional response or it will never be triggered. Click the response you just added, and use the up arrow to move it up, and then click Save.
13. Test your changes by using the following script.





 Speaker Utterance 

 You i want to make a reservation 
 Watson I can make a reservation for you. Just tell me the day and time of the reservation, and how many people it is for. 
 You tomorrow
You have an absence alert attached to this view that is configured to send a notification after 30 minutes. Because the view is not active, the absence alert is muted and you do not get notifications. To make the view active and get notifications for the absence condition, events need to start flowing into the view.







 Alert conditions 

You can configure any of the following triggering conditions for each notification channel that you configure for an alert:



* Time frequency: You set this condition to specify how often to trigger an alert. Valid values are: 30 seconds, 1 minute, 5 minutes, 15 minutes, 30 minutes, 1 hour, 6 hours, 12 hours, 24 hours
* Event lines counter: You set this condition to specify the number of event lines that match the view's filtering and search criteria. When the number of event lines is reached, an alert is triggered.



You can decide whether both conditions are checked or only one. If both conditions are set, an alert is triggered when any of the thresholds is reached.

For example, you can configure an alert that is triggered after 30 seconds, or when a 100 event lines that match the view's filtering and search criteria are collected.





 Notification channels 

You can define 1 or more notification channels for an alert.

The following table lists the notification channels that you can configure when an alert is triggered:



Notification channels

 Channel Configuration details 

 email You can configure one or more email addresses. For more information, see [Integrating with email](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-email). 
 SMS You can send an SMS to notify of an alert either through the PagerDuty channel or through the IBM Cloud Monitoring channel. For more information, see [Integrating with SMS](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-sms). 
 Slack You can configure a slack channel. 
 Webhook You can configure a web hook URL. 
 PagerDuty You can configure connection details to your PagerDuty system, and select a service.