-
Notifications
You must be signed in to change notification settings - Fork 155
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.
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
Always changed aws.apigatewayv2.Stage.defaultRouteSettings.loggingLevel
#2364
Labels
area/providers
awaiting-upstream
The issue cannot be resolved without action in another repository (may be owned by Pulumi).
kind/bug
Some behavior is incorrect or out of spec
service/apigatewayv2
Comments
ViktorCollin
added
kind/bug
Some behavior is incorrect or out of spec
needs-triage
Needs attention from the triage team
labels
Feb 13, 2023
Confirmed, with this program: "use strict";
const pulumi = require("@pulumi/pulumi");
const aws = require("@pulumi/aws");
const awsx = require("@pulumi/awsx");
const example = new aws.apigatewayv2.Api("example", {
protocolType: "HTTP",
});
const apiStage = new aws.apigatewayv2.Stage(
'stage',
{
apiId: example.id,
defaultRouteSettings: { loggingLevel: 'ERROR' }
},
); When I run
|
squaremo
added
area/providers
and removed
needs-triage
Needs attention from the triage team
labels
Feb 14, 2023
thomas11
added
the
bug/diff
kind/bug related to Pulumi generating wrong diffs on preview or up.
label
Apr 26, 2023
8 tasks
I ran into this same issue but with the args |
t0yv0
removed
the
bug/diff
kind/bug related to Pulumi generating wrong diffs on preview or up.
label
Sep 24, 2024
This seems to reproduce upstream hashicorp/terraform-provider-aws#39477 and we inherit the behavior. |
Might not be ideal but can workaround with: import * as pulumi from "@pulumi/pulumi";
import * as aws from "@pulumi/aws";
import * as awsx from "@pulumi/awsx";
const example = new aws.apigatewayv2.Api("example", {
protocolType: "HTTP",
});
const apiStage = new aws.apigatewayv2.Stage(
'stage',
{
apiId: example.id,
defaultRouteSettings: { loggingLevel: 'ERROR' }
},
{
ignoreChanges: ["defaultRouteSettings"]
}
); |
t0yv0
added
awaiting-upstream
The issue cannot be resolved without action in another repository (may be owned by Pulumi).
service/apigatewayv2
labels
Sep 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/providers
awaiting-upstream
The issue cannot be resolved without action in another repository (may be owned by Pulumi).
kind/bug
Some behavior is incorrect or out of spec
service/apigatewayv2
What happened?
Creating a resource of type
aws.apigatewayv2.Stage
with a propertydefaultRouteSettings.loggingLevel
set to eitherERROR
orINFO
will always report a diff[diff: ~defaultRouteSettings]
As far as i can find there is no logging level setting for HTTP API (https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-logging.html) it is only relevant for REST API
Expected Behavior
I don't expect there to be any diff between two consecutive runs of
pulumi up
Steps to reproduce
pulumi up
2 Run
pulumi preview
orpulumi up
it will display a diff which is unexpectedOutput of
pulumi about
CLI
Version 3.54.0
Go Version go1.19.5
Go Compiler gc
Plugins
NAME VERSION
aws 5.29.1
aws-apigateway 1.0.1
docker 3.6.1
nodejs unknown
Host
OS darwin
Version 12.6
Arch x86_64
This project is written in nodejs: executable='...node' version='v16.18.0'
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).
The text was updated successfully, but these errors were encountered: