Skip to content

Fix attach_content on Confluence Server with an existing attachement #1679

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gonchik merged 1 commit into from
Sep 10, 2026
Merged

Fix attach_content on Confluence Server with an existing attachement #1679

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 19 additions & 8 deletions atlassian/confluence/server/__init__.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1279,15 +1279,26 @@ def attach_content(
pass

if existing_attachment:
# Update existing attachment using PUT on the specific attachment ID
# Update existing attachment on the specific attachment ID
attachment_id = existing_attachment["id"]
update_path = f"rest/api/content/{attachment_id}"
response = self.put(
path=update_path,
data=data,
headers=headers,
files={"file": (name, content, content_type)},
)
if self.api_version == "1.0":
# older API versions use POST on data path below the child
update_path = f"{path}/{attachment_id}/data"
response = self.post(
path=update_path,
data=data,
headers=headers,
files={"file": (name, content, content_type)},
)
else:
# newer API versions use PUT on a path derived from the attachment ID directly
update_path = f"rest/api/content/{attachment_id}"
response = self.put(
path=update_path,
data=data,
headers=headers,
files={"file": (name, content, content_type)},
)
else:
# Create new attachment using POST
response = self.post(
Expand Down
Loading