generated from pulumi/pulumi-provider-boilerplate
-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Labels
kind/bugSome behavior is incorrect or out of specSome behavior is incorrect or out of spec
Description
Describe what happened
i just upgraded from pulumi 3.187.0 to 3.191.0 and i'm now getting this warning:
warning: provider attempted to use __internal key that is reserved by the engine
for the docker-build provider.
Sample program
i haven't tried reducing this to a standalone program, but i can try to do that if it doesn't easily reproduce
Log output
No response
Affected Resource(s)
No response
Output of pulumi about
CLI
Version 3.191.0
Go Version go1.25.0
Go Compiler gc
Plugins
KIND NAME VERSION
resource aws 6.83.0
resource cloudinit 1.4.13
resource cockroach 0.9.4
resource command 0.9.2
resource docker-build 0.0.12
resource fivetran 0.1.12
resource frontegg 0.2.36
resource kubernetes 4.23.0
resource pulumi_crds 0.0.0
resource purrl 0.6.2
language python 3.191.0
resource random 4.18.3
resource snowflake 0.60.0
resource tls 5.2.1
Host
OS arch
Version
Arch x86_64
This project is written in python: executable='/home/doy/materialize/cloud/venv/bin/python' version='3.13.5'
Current Stack: materialize/mzcloud/doy
TYPE URN
<snip>
Found no pending operations associated with materialize/doy
Backend
Name pulumi.com
URL https://app.pulumi.com/doy-materialize-com
User doy-materialize-com
Organizations doy-materialize-com, materialize
Token type personal
Dependencies:
NAME VERSION
aiohttp 3.12.14
bcrypt 4.3.0
boto3 1.38.8
boto3-stubs 1.38.8
click 8.1.8
colored 2.3.0
deepmerge 2.0
frontegg_api 0.0.1
Jinja2 3.1.6
jsonschema 4.23.0
launchdarkly-server-sdk 9.11.0
materialize 0.2.0
mypy-boto3-acm 1.38.38
mypy-boto3-ec2 1.38.45
mypy-boto3-eks 1.38.35
mypy-boto3-elb 1.38.0
mypy-boto3-elbv2 1.38.43
mypy-boto3-iam 1.38.14
mypy-boto3-kms 1.38.45
mypy-boto3-resourcegroupstaggingapi 1.38.0
mypy-boto3-route53 1.38.32
mypy-boto3-s3 1.38.44
mypy-boto3-secretsmanager 1.38.0
mypy-boto3-ssm 1.38.5
mypy-boto3-sts 1.38.38
pre_commit 4.2.0
psutil 7.0.0
psycopg 3.2.3
psycopg-binary 3.2.3
pulumi_aws 6.83.0
pulumi_cloudinit 1.4.13
pulumi-command 0.9.2
pulumi_crds 0.0.0
pulumi_docker_build 0.0.12
pulumi_fivetran 0.1.12
pulumi_frontegg 0.2.36
pulumi_kubernetes 4.23.0
pulumi_random 4.18.3
pulumi_snowflake 0.60.0
pulumi_tls 5.2.1
pulumiverse_cockroach 0.9.4
pulumiverse_purrl 0.6.2
pyelftools 0.32
PyJWT 2.10.1
pyOpenSSL 25.0.0
pytest-xdist 3.6.1
python-frontmatter 1.1.0
retry 0.9.2
ruamel.yaml 0.18.10
tabulate 0.9.0
toml 0.10.2
tomli_w 1.2.0
tqdm 4.67.1
types-psutil 7.0.0.20250601
types-pyOpenSSL 24.1.0.20240722
wheel 0.45.1
xxhash 3.5.0
zstandard 0.23.0
Pulumi locates its logs in /tmp by default
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
mkourbaj and purificant
Metadata
Metadata
Assignees
Labels
kind/bugSome behavior is incorrect or out of specSome behavior is incorrect or out of spec