Skip to content

feat: add ACTOR_PERMISSION_LEVEL to the configuration #689

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
merged 5 commits into from
Nov 28, 2025
Merged

feat: add ACTOR_PERMISSION_LEVEL to the configuration #689

Changes from 3 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
9cd910d
feat: add actor permissions to the configuration
stepskop Nov 25, 2025
2457458
feat: log the actor permission on actor initialization
stepskop Nov 25, 2025
f2f0ca7
Revert "feat: log the actor permission on actor initialization"
stepskop Nov 27, 2025
a0b42d5
chore: use single alias
stepskop Nov 27, 2025
7b5c3c6
chore: no need for alias as the property name is the same
stepskop Nov 28, 2025
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
11 changes: 11 additions & 0 deletions src/apify/_configuration.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,6 +61,17 @@ class Configuration(CrawleeConfiguration):
),
] = None

actor_permission_level: Annotated[
str | None,
Field(
validation_alias=AliasChoices(
'actor_permission_level',
'apify_actor_permission_level',
Copy link
Contributor

@janbuchar janbuchar Nov 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it really make sense to have multiple choices for a newly introduced variable? The aliases exist mainly for compatibility with outdated documentation 😁

Copy link
Contributor Author

@stepskop stepskop Nov 27, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, I wasn't sure how the name was inferred, so it was just to be sure 😅.

So in this case, the actor_permission_level should be enough, right?

The name of the env var is ACTOR_PERMISSION_LEVEL and it is part of ActorEnvVars in apify-shared-python.

https://github.com/apify/apify-shared-python/blob/782a8334e2d0e5de38aa28e10f4f1f1038497955/src/apify_shared/consts.py#L136

e.g.: I assume that it won't be prefixed.

Copy link
Contributor

@janbuchar janbuchar Nov 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, we can keep just actor_permission_level and drop apify_actor_permission_level

),
description='Permission level the Actor is run under.',
),
] = None

actor_run_id: Annotated[
str | None,
Field(
Expand Down