Support expired_object_delete_marker in OBS lifecycle policies

[gysel]

According to #1114 (comment), ExpiredObjectDeleteMarker is now supported in OBS. Can you please add support for this field in opentelekomcloud_obs_bucket? It is already available in opentelekomcloud_s3_bucket.

Related to #1143

[artem-lifshits]

Hello @gysel according to documentation there's no such parameter at the moment.
Please open a demand for OTC support to include this paramter to API and we will implement it once it's available.

[gysel]

Then the documentation is wrong too. I tested the API and the parameter works.

And maybe re-read this comment too: #1114 (comment) ;-)

[artem-lifshits]

@gysel I can't add this parameter to OBS lifecycle right now.

According to our guidelines, we only implement documented features. I checked and ExpiredObjectDeleteMarker isn't officially documented for either S3 or OBS at the moment.

I've opened an internal ticket to get clarification on this.
If you open a support ticket requesting this feature it'll move much faster.

[gysel]

Thanks for the update. I'll create a support ticket.

[dsabelni]

Hello @gysel , if possible, could you please share a working example of the API request containing the ExpiredObjectDeleteMarker ? I've tried it on all environments for both OBS and S3 API and it didn't work for me.

My request and responses examples:

PUT /?lifecycle HTTP/1.1
Authorization: OBS generated_signature_value
Host: ds-postman-test-bucket.obs.eu-de.otc.t-systems.com
Date: Wed, 17 Dec 2025 15:05:19 GMT
Content-MD5: jiid4QWsJM47KI2dCYgzaQ==
Accept: */*
Postman-Token: 1fd8a528-2b85-42cc-b525-a7f0cc73dce4
Content-Length: 540
 
<LifecycleConfiguration>
	<Rule>
		<ID>lifecycle-rule-id</ID>
		<Filter>
			<Tag>
				<Key>key1</Key>
				<Value>value1</Value>
			</Tag>
		</Filter>
		<Status>Enabled</Status>
		<Expiration>
			<ExpiredObjectDeleteMarker>true</ExpiredObjectDeleteMarker>
		</Expiration>
		<NoncurrentVersionExpiration>
			<NoncurrentDays>70</NoncurrentDays>
		</NoncurrentVersionExpiration>
	</Rule>
</LifecycleConfiguration>
 
HTTP/1.1 400 Bad Request
Server: OBS
x-obs-request-id: 0000019B2CD81F466849E9023CABBD76
x-obs-id-2: 36AAAQAAEAABAAAQAAEAABAAAQAAEAABAAAaI=AAAAAAAAAAAAAAAAAAAAAAAAAA
Content-Type: application/xml
Date: Wed, 17 Dec 2025 15:05:19 GMT
Content-Length: 339
 
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Error>
	<Code>MalformedXML</Code>
	<Message>The XML you provided was not well-formed or did not validate against our published schema</Message>
	<RequestId>0000019B2CD81F466849E9023CABBD76</RequestId>
	<HostId>SKeXvTLONkbAMA5IYblEvLmBFd1/UlLhyt7HZs8T0Z/PLfeIljfhG+SPKRJMqqvl</HostId>
</Error>

PUT /?lifecycle HTTP/1.1
Host: ds-postman-test-bucket.obs.eu-de.otc.t-systems.com
X-Amz-Content-Sha256: 92b82abf8a340c5200e94d3e37e53b3dd3eede04641cdbaf66be80334f62ea89
X-Amz-Date: 20251217T150551Z
Authorization: AWS4-HMAC-SHA256 generated_signature_value
Content-Type: application/xml
User-Agent: PostmanRuntime/7.51.0
Accept: */*
Postman-Token: 7d6d7d1d-8f6d-467e-b7b9-f3bfa7d1e409
Accept-Encoding: gzip, deflate, br
Connection: keep-alive
Content-Length: 540
 
<LifecycleConfiguration>
	<Rule>
		<ID>lifecycle-rule-id</ID>
		<Filter>
			<Tag>
				<Key>key1</Key>
				<Value>value1</Value>
			</Tag>
		</Filter>
		<Status>Enabled</Status>
		<Expiration>
			<ExpiredObjectDeleteMarker>true</ExpiredObjectDeleteMarker>
		</Expiration>
		<NoncurrentVersionExpiration>
			<NoncurrentDays>70</NoncurrentDays>
		</NoncurrentVersionExpiration>
	</Rule>
</LifecycleConfiguration>
 
HTTP/1.1 400 Bad Request
Server: OBS
x-reserved: amazon, aws and amazon web services are trademarks or registered trademarks of Amazon Technologies, Inc
x-amz-request-id: 0000019B2CD89A1941CB1D2F5C9BBF46
x-amz-id-2: 36AAAQAAEAABAAAQAAEAABAAAQAAEAABAAAaI=AAAAAAAAAAAAAAAAAAAAAAAAAA
Content-Type: application/xml
Date: Wed, 17 Dec 2025 15:05:51 GMT
Content-Length: 339
 
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Error>
	<Code>MalformedXML</Code>
	<Message>The XML you provided was not well-formed or did not validate against our published schema</Message>
	<RequestId>0000019B2CD89A1941CB1D2F5C9BBF46</RequestId>
	<HostId>Z2kIr02IUCEv/m6g6kvdOe1mZnw/1LehztSjiRQcOP7Xqtu8gxnn8qXYMw9QG/J8</HostId>
</Error>

[gysel]

Sure, here is my request:

PUT /?lifecycle HTTP/1.1
X-Amz-Content-Sha256: 65ae7c1236b5c498ea2dc15562f8e4f53dda820b452fefeac536ff335708e71f
Host: <REDACTED>.obs.eu-ch2.sc.otc.t-systems.com
X-Amz-Date: 20251218T064304Z
Authorization: AWS4-HMAC-SHA256 <REDACTED>
Content-Type: application/xml
User-Agent: PostmanRuntime/7.48.0
Accept: */*
Postman-Token: 83d6bc96-c5fa-4924-a2e3-ace9f4f6b327
Accept-Encoding: gzip, deflate, br
Connection: keep-alive
Content-Length: 537
 
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<LifecycleConfiguration xmlns="http://obs.eu-ch2.sc.otc.t-systems.com/doc/2021-08-20/">
<Rule>
<ID>noncurrent-version-expiration</ID>
<Prefix></Prefix>
<Status>Enabled</Status>
<NoncurrentVersionExpiration>
<NoncurrentDays>7</NoncurrentDays>
</NoncurrentVersionExpiration>
<Expiration>
<ExpiredObjectDeleteMarker>true</ExpiredObjectDeleteMarker>
</Expiration>
</Rule>
</LifecycleConfiguration>
 
HTTP/1.1 200 OK
Server: OBS
x-reserved: amazon, aws and amazon web services are trademarks or registered trademarks of Amazon Technologies, Inc
x-amz-request-id: 0000019B3032A6478143CECEE2108C7C
x-amz-id-2: 36AAAQAAEAABSAAgAAEAABAAAQAAEAABAAAaI=AAAAAAAAAAAAAAAAAAAAAAAAAA
Date: Thu, 18 Dec 2025 06:43:04 GMT
Content-Length: 0

[dsabelni]

Thank you @gysel , using request body provided by you worked for me as well. I've created an internal demand ticket requesting to update the documentation.