https://pulumi.com
Join Slack
We've noticed that we consistently get this error when running `up` , although everything seems to w...
# general
h
We've noticed that we consistently get this error when running 
up
, although everything seems to work normally afterwards:
Copy code
[INFO]	2025-03-19T14:09:44.675Z	e8b6ba5d-8f7b-4af8-a3b0-64e4de2a3e8e	updating stack...
Updating (mdl-2tvCAzbsAdOpo5KfOAxH0ocpXXX-crawling-mussel2):
[ERROR]	2025-03-19T14:09:45.092Z	e8b6ba5d-8f7b-4af8-a3b0-64e4de2a3e8e	Exception calling application: Method not implemented!
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/grpc/_server.py", line 610, in _call_behavior
response_or_iterator = behavior(argument, context)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pulumi/runtime/proto/language_pb2_grpc.py", line 137, in GetRequiredPackages
raise NotImplementedError('Method not implemented!')
NotImplementedError: Method not implemented!
@ updating....
+  pulumi:pulumi:Stack model_services-mdl-2tvCAzbsAdOpo5KfOAxH0ocpXXX-crawling-mussel2 creating (0s)
@ updating....
Is this expected or is there something we should address here?
e
That's not expected, is this with just a normal python pulumi program or with automation api?
h
Hi there! This is using the automation API
We dug into the code and it seems there are a bunch of grpc calls that just raise NotImplemented
Just in case these help:
Copy code
stack = auto.create_or_select_stack(
            stack_name=stack_name,
            project_name=project_name,
            program=model_services_stack([model]),
            opts=auto.LocalWorkspaceOptions(
                secrets_provider=SECRET_PROVIDER,
                project_settings=auto.ProjectSettings(
                    name=project_name,
                    runtime="python",
                    backend=auto.ProjectBackend(BACKEND_URL),
                ),
                stack_settings={
                    stack_name: auto.StackSettings(secrets_provider=SECRET_PROVIDER)
                },
            ),
        )
Copy code
up_res = stack.up(
                on_output=print,
                diff=SHOW_DIFF,
                continue_on_error=CONTINUE_ON_ERROR,
                debug=LOG_LEVEL == "DEBUG",
                log_verbosity=3 if LOG_LEVEL == "DEBUG" else 0,
            )
e
yeh but not sure why they're showing up in logs, might be this is python grpc auto logging things and we didn't notice
I think it's safe to ignore this but do raise an issue so we can see about making it cleaner
h
The gotcha to it for us was that we are running this in a Lambda, and, originally, we had just the default small memory/cpu settings and it would print this error and then sit for minutes leaving us thinking that it was broken, but actually just upping the resources showed us that it was not catastrophic
I'll put it in as an issue
Should I just use pulumi/pulumi? I don't see an automation repo right away
e
yeh just pulumi/pulumi
it's always fine to raise any issue there, if there's a better place for it we'll move it
h
Sorry to bug you... I've given this a few tries and it isn't coming easy.... How can I find where the Pulumi.yaml is for a project created using the automation API? This is all running in a lambda so I can't access it mid-stride
This is so that I can run 
pulumi about
for the issue, but it currently reports it can't find any projects
Or maybe there is an 
auto.about()
that I haven't spotted?
e
Just give us the global pulumi about. It's mostly so we know the CLI version
h
e
Thanks
33 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by