-
Notifications
You must be signed in to change notification settings - Fork 113
Add APM agent configuration #1196
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
base: main
Are you sure you want to change the base?
Conversation
Steps: []resource.TestStep{ | ||
{ | ||
Config: testAccResourceAgentConfigurationCreate(serviceName), | ||
Check: resource.ComposeTestCheckFunc( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO it makes sense to check id
too.
tflog.Trace(ctx, fmt.Sprintf("Created APM agent configuration with ID: %s", id)) | ||
|
||
resp.Diagnostics.Append(resp.State.Set(ctx, &plan)...) | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think some resources in this provider (maybe ones based on SDKv2) call read
in scope of create
/update
calls but it seems we don't use this pattern here. IIRC, the EC provider also calls read
inside create
/update
calls. Does it make sense to do this here too?
Co-authored-by: Dmitry Onishchenko <8962171+dimuon@users.noreply.github.com>
Co-authored-by: Dmitry Onishchenko <8962171+dimuon@users.noreply.github.com>
The fix has been merged into Kibana/main
Fixes #315
A couple of things:
transform_schema
which I don't really want to add to unless it's strictly required. When these endpoints are eventually moved to the automatically generated schema (as opposed to the hand crafted one in use today), the existing code handling this header will kick in and we can tidy it up.