fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) by renovate[bot] · Pull Request #131 · devopsfactory-io/neptune

renovate · 2026-04-13T02:32:26Z

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Type	Update	Change	Pending
github.com/aws/aws-sdk-go-v2	require	minor	`v1.41.5` → `v1.47.2`	`v1.47.3`
github.com/aws/aws-sdk-go-v2/config	require	minor	`v1.32.14` → `v1.33.8`	`v1.33.9`
github.com/aws/aws-sdk-go-v2/service/s3	require	minor	`v1.98.0` → `v1.114.2`	`v1.114.3`
github.com/aws/aws-sdk-go-v2/service/secretsmanager	require	minor	`v1.41.5` → `v1.50.3`	`v1.50.4`

Release Notes

aws/aws-sdk-go-v2 (github.com/aws/aws-sdk-go-v2)

`v1.47.2`

Compare Source

Module Highlights

github.com/aws/aws-sdk-go-v2/service/customerprofiles: v1.49.0
- Feature: The release updates standard profile with 2 new fields that supports account-level engagement. Updated APIs include CreateProfile, UpdateProfile, MergeProfiles, SearchProfiles, BatchGetProfile, GetSegmentMembership, CreateSegmentDefinition, CreateSegmentEstimate.
github.com/aws/aws-sdk-go-v2/service/ec2: v1.239.0
- Feature: Added support for the force option for the EC2 instance terminate command. This feature enables customers to recover resources associated with an instance stuck in the shutting-down state as a result of rare issues caused by a frozen operating system or an underlying hardware problem.
github.com/aws/aws-sdk-go-v2/service/elasticloadbalancingv2: v1.47.2
- Documentation: This release enables secondary IP addresses for Network Load Balancers.
github.com/aws/aws-sdk-go-v2/service/entityresolution: v1.21.0
- Feature: Add support for creating advanced rule-based matching workflows in AWS Entity Resolution.
github.com/aws/aws-sdk-go-v2/service/glue: v1.121.0
- Feature: Added support for Route node, S3 Iceberg sources/targets, catalog Iceberg sources, DynamoDB ELT connector, AutoDataQuality evaluation, enhanced PII detection with redaction, Kinesis fan-out support, and new R-series worker types.
github.com/aws/aws-sdk-go-v2/service/inspector2: v1.40.0
- Feature: Extend usage to include agentless hours and add CODE_REPOSITORY to aggregation resource type
github.com/aws/aws-sdk-go-v2/service/iot: v1.66.0
- Feature: This release allows AWS IoT Core users to use their own AWS KMS keys for data protection
github.com/aws/aws-sdk-go-v2/service/opensearch: v1.49.0
- Feature: Granular access control support for NEO-SAML with IAMFederation for AOS data source
github.com/aws/aws-sdk-go-v2/service/quicksight: v1.90.0
- Feature: Added Impala connector support
github.com/aws/aws-sdk-go-v2/service/s3control: v1.62.0
- Feature: Add Tags field to CreateAccessPoint
github.com/aws/aws-sdk-go-v2/service/sesv2: v1.49.0
- Feature: This release introduces support for Multi-tenant management
github.com/aws/aws-sdk-go-v2/service/workspacesweb: v1.29.0
- Feature: Added ability to log session activity on a portal to an S3 bucket.

`v1.47.1`

Compare Source

Module Highlights

github.com/aws/aws-sdk-go-v2/service/bedrockagentcore: v1.49.0
- Feature: Batch evaluation now supports evaluating specific traces within a session. Each session can specify up to 100 trace IDs to evaluate.
github.com/aws/aws-sdk-go-v2/service/connect: v1.200.0
- Feature: Made the replicaAlias attribute optional in the ReplicateInstance API to support Global routing for Amazon Connect Global Resiliency (ACGR) instances. This change maintains backward compatibility. When onboarding to ACGR without Global routing, you must specify a custom replicaAlias in your API call
github.com/aws/aws-sdk-go-v2/service/ec2: v1.334.0
- Feature: Adding support for "Tunnel" VPC Endpoint
github.com/aws/aws-sdk-go-v2/service/guardduty: v1.93.0
- Feature: This change surfaces AI Protection resources on existing public IAM attack sequences. Customers will now see which model was accessed and whether a guardrail intervened as part of the credential-compromise sequence.
github.com/aws/aws-sdk-go-v2/service/iotwireless: v1.65.0
- Feature: Adds Multi-frame GNSS support to the AWS IoT Core Device Location GetPositionEstimate API. The new GnssMultiFrame measurement type improves location accuracy by combining multiple GNSS signal captures (2, 4, 8, 16, or 32) from the same device to estimate its position.
github.com/aws/aws-sdk-go-v2/service/notifications: v1.17.0
- Feature: Added support for attachments on managed notification events. Added support to access and subscribe sensitive managed notification events.
github.com/aws/aws-sdk-go-v2/service/sesv2: v1.74.0
- Feature: Added support to query the tenant name for BatchGetMetricData and CreateExportJob APIs to filter metrics and messages at the tenant level.
github.com/aws/aws-sdk-go-v2/service/sns: v1.47.1
- Documentation: SNS API reference documentation update
github.com/aws/aws-sdk-go-v2/service/socialmessaging: v1.21.0
- Feature: Add support for WhatsApp Calling APIs.
github.com/aws/aws-sdk-go-v2/service/vpclattice: v1.33.0
- Feature: Adding support for CIDR Resource Configuration

`v1.47.0`

Compare Source

General Highlights

Dependency Update: Updated to the latest SDK module versions

Module Highlights

github.com/aws/aws-sdk-go-v2/service/aiops: v1.17.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/amplifybackend: v1.43.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/amplifyuibuilder: v1.39.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/apigateway: v1.51.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/apigatewaymanagementapi: v1.40.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/apigatewayv2: v1.45.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/appfabric: v1.27.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/appintegrations: v1.50.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/applicationcostprofiler: v1.38.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/applicationsignals: v1.33.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/arczonalshift: v1.33.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/artifact: v1.28.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/backup: v1.68.0
- Feature: Enable schema-based (de)serialization for this service.
- Bug Fix: BREAKING CHANGE: The ValidationWindowHours field on RestoreTestingSelectionForCreate and RestoreTestingSelectionForUpdate has been changed from int32 to *int32. Before this change, the field was incorrectly marked as having a default value of 0 by the service, which made it functionally impossible for users to set it to 0 in an UpdateRestoreTestingSelection call.
github.com/aws/aws-sdk-go-v2/service/costoptimizationhub: v1.34.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/databasemigrationservice: v1.74.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/datapipeline: v1.41.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/devicefarm: v1.51.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/directconnect: v1.54.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/dynamodbstreams: v1.44.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/ec2instanceconnect: v1.43.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/eks: v1.103.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/evs: v1.23.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/freetier: v1.24.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/glue: v1.168.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/guardduty: v1.98.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/health: v1.49.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/healthlake: v1.52.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/identitystore: v1.48.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/invoicing: v1.23.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/iotthingsgraph: v1.41.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/keyspaces: v1.36.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/keyspacesstreams: v1.18.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/lambda: v1.111.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/lambdacore: v1.10.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/lambdamicrovms: v1.10.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/lambdaweb: v1.1.0
- Feature: Removes operations that are not yet generally available from the Lambda Web.
github.com/aws/aws-sdk-go-v2/service/lookoutequipment: v1.47.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/marketplaceagreement: v1.29.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/mturk: v1.41.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/mwaaserverless: v1.12.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/networkfirewall: v1.75.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/odb: v1.25.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/opensearch: v1.84.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/partnercentralaccount: v1.16.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/partnercentralbenefits: v1.11.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/pinpointemail: v1.40.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/quicksight: v1.135.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/sagemakeredge: v1.42.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/sagemakerfeaturestoreruntime: v1.47.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/sagemakermetrics: v1.29.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/sesv2: v1.78.0
- Feature: Enable schema-based (de)serialization for this service.

`v1.46.0`

Compare Source

Module Highlights

github.com/aws/aws-sdk-go-v2/service/deadline: v1.44.0
- Feature: The new ListMemberships API enables users to discover their memberships across Deadline Cloud resources, enabling scoped users of Deadline resources to discover and interact with the resources they have been provided scoped access to.
github.com/aws/aws-sdk-go-v2/service/marketplacemetering: v1.46.0
- Feature: AWS Marketplace Metering Service adds AgreementId to ResolveCustomer API response.
github.com/aws/aws-sdk-go-v2/service/mediatailor: v1.73.0
- Feature: Add caching settings to http functions
github.com/aws/aws-sdk-go-v2/service/quicksight: v1.137.0
- Feature: Adds granular custom permissions for the Gong action connector (GongAction, CreateAndUpdateGongAction, ShareGongAction, UseGongAction) and for create, update, and share operations on 45 data source connectors, such as Amazon S3 and Snowflake, through the Custom Permissions APIs.
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/securityagent: v1.24.0
- Feature: Adds a test scope field to specify whether a pentest targets a web application or a generative AI application.

`v1.45.1`

Compare Source

General Highlights

Dependency Update: Updated to the latest SDK module versions

Module Highlights

github.com/aws/aws-sdk-go-v2: v1.45.1
- Bug Fix: Fix internal timeout gate to not depend on env opt-in.
github.com/aws/aws-sdk-go-v2/feature/s3/transfermanager: v0.4.1
- Bug Fix: Fix DownloadObject bug so parts can be read to correct offset regardless of parts sizes change
- Bug Fix: Fix GetObject bug so object parts can be read to correct offset regardless of parts sizes change

`v1.45.0`

Compare Source

Module Highlights

github.com/aws/aws-sdk-go-v2/service/agentregistrycontrol: v1.8.0
- Feature: AWS Agent Registry is improving recently launched custom metadata schema feature to make shared attributes easier to manage.
github.com/aws/aws-sdk-go-v2/service/appintegrations: v1.52.0
- Feature: This release adds the Connect JWT authentication type and the AudienceOverride field to AuthConfig, letting A2A server applications authenticate with JWTs issued by Amazon Connect.
github.com/aws/aws-sdk-go-v2/service/appstream: v1.72.0
- Feature: Adds support for administrators to require users to re-authenticate OneDrive and Google Drive storage connectors when a streaming session is reused.
github.com/aws/aws-sdk-go-v2/service/arcregionswitch: v1.21.0
- Feature: Adds support for SSM Execution Block in Region switch plans
github.com/aws/aws-sdk-go-v2/service/connect: v1.205.0
- Feature: New APIs to support aliases and versions for ContactFlow.
github.com/aws/aws-sdk-go-v2/service/datasync: v1.68.0
- Feature: AWS DataSync Enhanced mode now supports FSx for OpenZFS, NFS 4.2, and object metadata controls
github.com/aws/aws-sdk-go-v2/service/gamelift: v1.68.0
- Feature: Adds support for new instance types in the C8a, C8i, C9g, M8a, M8i, and M9g families for managed EC2 and container fleets
github.com/aws/aws-sdk-go-v2/service/glue: v1.171.0
- Feature: Amazon Glue releasing support for adding custom namespace for S3 Tables in Glue zero-ETL integration
github.com/aws/aws-sdk-go-v2/service/lakeformation: v1.56.0
- Feature: Added new LakeFormation APIs and documentation updates for Simple Row-level Security (RLS).
github.com/aws/aws-sdk-go-v2/service/lambdaweb: v1.2.1
- Documentation: Documentation update to include common use cases.
github.com/aws/aws-sdk-go-v2/service/omics: v1.57.0
- Feature: With Expanded container registry support, you can use container images from registries such as Seqera (Wave), NVIDIA NGC, and Google Artifact Registry with AWS HealthOmics private workflows, without manually migrating images into Amazon ECR or editing your workflow definitions.
github.com/aws/aws-sdk-go-v2/service/resiliencehubv2: v1.13.0
- Feature: Adds support for DevOpsAgent integration where users can specify the agent space ARN at service level and launch investigations directly from Resilience Hub v2.
github.com/aws/aws-sdk-go-v2/service/route53domains: v1.45.0
- Feature: Route 53 Domains now supports premium domains. This release adds consent objects to operations on premium domains and a new GetDomainPrices API. Also, the Flags and PublicKey fields were deprecated from the DnssecKey response.
github.com/aws/aws-sdk-go-v2/service/sagemaker: v1.284.0
- Feature: Adds Amazon Athena, Cleanup, ForEach, and Amazon EMR Serverless step metadata, ForEach iteration context, and the CompletedWithFailures execution status to SageMaker Pipelines.
github.com/aws/aws-sdk-go-v2/service/securityhub: v1.85.0
- Feature: Adds and updates APIs to support criticality. This feature allows customers to create automation rules to assign criticality to resources matching a criteria. With this release, resources and exposure findings will include the criticality.

`v1.44.0`

Compare Source

Module Highlights

github.com/aws/aws-sdk-go-v2/service/deadline: v1.44.0
- Feature: The new ListMemberships API enables users to discover their memberships across Deadline Cloud resources, enabling scoped users of Deadline resources to discover and interact with the resources they have been provided scoped access to.
github.com/aws/aws-sdk-go-v2/service/marketplacemetering: v1.46.0
- Feature: AWS Marketplace Metering Service adds AgreementId to ResolveCustomer API response.
github.com/aws/aws-sdk-go-v2/service/mediatailor: v1.73.0
- Feature: Add caching settings to http functions
github.com/aws/aws-sdk-go-v2/service/quicksight: v1.137.0
- Feature: Adds granular custom permissions for the Gong action connector (GongAction, CreateAndUpdateGongAction, ShareGongAction, UseGongAction) and for create, update, and share operations on 45 data source connectors, such as Amazon S3 and Snowflake, through the Custom Permissions APIs.
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/securityagent: v1.24.0
- Feature: Adds a test scope field to specify whether a pentest targets a web application or a generative AI application.

`v1.43.8`

Compare Source

General Highlights

Dependency Update: Update to smithy-go v1.27.10.
Dependency Update: Updated to the latest SDK module versions

Module Highlights

github.com/aws/aws-sdk-go-v2: v1.43.8
- Bug Fix: Make X-Amz-Checksum-Mode appear on query parameters on presigned URLs
github.com/aws/aws-sdk-go-v2/service/account: v1.36.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/acmpca: v1.51.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/autoscaling: v1.73.0
- Feature: Adds support for Distribution Segments in mixed instances policies, providing ordered prioritization across On-Demand Capacity Reservations, Capacity Blocks, interruptible Capacity Reservations, and On-Demand capacity.
github.com/aws/aws-sdk-go-v2/service/billingconductor: v1.33.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/cloudcontrol: v1.33.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/cloudhsmv2: v1.38.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/cloudwatchevents: v1.36.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/codebuild: v1.73.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/codegurureviewer: v1.38.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/codepipeline: v1.50.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/dataexchange: v1.45.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/deadline: v1.37.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/detective: v1.42.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/devopsagent: v1.11.0
- Feature: Adds the UpdateApprovalAction API for resolving agent action approvals in AWS DevOps Agent agent spaces.
github.com/aws/aws-sdk-go-v2/service/directoryservice: v1.42.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/drs: v1.44.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/ec2: v1.323.0
- Feature: Fleet feature to support Capacity Reservation Resource Groups with Amazon EC2 Capacity Blocks and interruptible Capacity Reservations
github.com/aws/aws-sdk-go-v2/service/eks: v1.93.0
- Feature: This feature would give customers the ability to tune TerminatedPodGcThreshold configuration in an Amazon EKS cluster.
github.com/aws/aws-sdk-go-v2/service/emrcontainers: v1.46.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/eventbridge: v1.49.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/evs: v1.14.0
- Feature: EVS now supports i7i.metal-48xl EC2 bare metal instance type, delivering high random IOPS performance with real-time latency, ideal for IO intensive and latency-sensitive workloads such as transactional databases, real-time analytics, and AI ML pre-processing.
github.com/aws/aws-sdk-go-v2/service/frauddetector: v1.45.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/fsx: v1.69.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/globalaccelerator: v1.39.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/iamtoolbox: v1.0.0
- Release: New AWS service client module
- Feature: AWS Identity and Access Management (IAM) announces access troubleshooter, helping you debug access denied errors faster. Supported error messages now include an identifier you can use to retrieve detailed evaluations of the policies considered and their results. Preview in US East (N. Virginia).
github.com/aws/aws-sdk-go-v2/service/inspector: v1.34.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/iot: v1.78.0
- Feature: As part of this release, we are extending capability of AWS IoT Rules Engine to support IoT InfluxDB Action. The IoT InfluxDB action lets customers send messages from IoT sensors and applications to InfluxDB.
github.com/aws/aws-sdk-go-v2/service/iotsecuretunneling: v1.37.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/iottwinmaker: v1.33.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/ivs: v1.56.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/ivsrealtime: v1.38.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/licensemanager: v1.42.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/marketplacecatalog: v1.46.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/marketplacemetering: v1.40.3
- Documentation: Updated documentation to clarify duplicate-billing prevention and BatchMeterUsage retry guidance
github.com/aws/aws-sdk-go-v2/service/mediapackage: v1.43.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/mediapackagevod: v1.43.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/mediastore: v1.33.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/networkmanager: v1.45.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/outposts: v1.68.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/paymentcryptography: v1.34.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/pi: v1.40.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/qconnect: v1.35.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/resourceexplorer2: v1.28.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/servicecatalogappregistry: v1.39.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/servicediscovery: v1.44.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/shield: v1.38.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/signer: v1.36.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/storagegateway: v1.47.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/swf: v1.38.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/transcribestreaming: v1.39.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/transfer: v1.76.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/translate: v1.37.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/voiceid: v1.34.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/vpclattice: v1.27.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/wafv2: v1.78.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/wisdom: v1.36.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/workspacesthinclient: v1.24.0
- Feature: Enable schema-based (de)serialization for this service.
github.com/aws/aws-sdk-go-v2/service/xray: v1.40.0
- Feature: Enable schema-based (de)serialization for this service.

`v1.43.7`

Compare Source

General Highlights

Dependency Update: Updated to the latest SDK module versions

Module Highlights

github.com/aws/aws-sdk-go-v2: v1.43.7
- Bug Fix: Make x-amz-checksum-* headers on presigner always show up as headers
github.com/aws/aws-sdk-go-v2/feature/s3/manager: v1.22.44
- Bug Fix: Fix flaky test from feature/s3/manager upload retry
github.com/aws/aws-sdk-go-v2/service/amplify: v1.42.0
- Feature: Increased the maximum allowed length from 255 to 4,096 characters to support longer access tokens.
github.com/aws/aws-sdk-go-v2/service/arcregionswitch: v1.14.0
- Feature: Adds support for Rds switchover read replica for Oracle databases in Region switch plans
github.com/aws/aws-sdk-go-v2/service/batch: v1.70.0
- Feature: AWS Batch now supports a new compute environment type that provides fully managed EC2 capacity with broader compute flexibility than Fargate, including GPU instances, bare metal, and specific instance type selection, without infrastructure management overhead.
github.com/aws/aws-sdk-go-v2/service/cloudfront: v1.68.0
- Feature: Added SigV4a as a supported signing protocol for Origin Access Control (OAC), enabling CloudFront to sign requests to Amazon S3 Multi-Region Access Point (S3-MRAP) origins.
github.com/aws/aws-sdk-go-v2/service/directconnect: v1.45.0
- Feature: This release adds custom route prefix pool allocations for Direct Connect. You can set IPv4 and IPv6 route prefix counts on private and transit virtual interfaces, and view pool size and unallocated counts on connections and LAGs, plus direct connect gateway attachment prefix allocation totals.
github.com/aws/aws-sdk-go-v2/service/ec2: v1.322.0
- Feature: EC2 marks UEFI instance metadata field as sensitive.
github.com/aws/aws-sdk-go-v2/service/lambda: v1.102.0
- Feature: Adds support for full JSON resource-based policies, enabling customers to create, retrieve, update, and delete function resource policies as complete JSON documents.
github.com/aws/aws-sdk-go-v2/service/pricingplanmanager: v1.0.5
- Documentation: Documentation update for the CreateSubscription API to correct the default value of the approval mode parameter. The default value for paid subscriptions is MANUAL, not IMMEDIATE as previously documented. The default value remains IMMEDIATE for FREE tier subscriptions.
github.com/aws/aws-sdk-go-v2/service/s3: v1.107.3
- Bug Fix: Expand S3 operations that check for an error inside an HTTP 200 response (wave 2/4)
- Bug Fix: Forward the original response body's Closer in S3 200-error handling instead of wrapping it in io.NopCloser, to avoid issues with TCP connection reuse (observed on CompleteMultipartUpload).
github.com/aws/aws-sdk-go-v2/service/sagemaker: v1.268.0
- Feature: Added IAM Identity Center (IdC) support to CreatePartnerApp and UpdatePartnerApp APIs. Added Customer Managed Key (CMK) support to CreateMlflowApp and DescribeMlflowApp.
github.com/aws/aws-sdk-go-v2/service/sesv2: v1.67.0
- Feature: Amazon SES now supports per-message tracking overrides. You can use the new ConfigurationOverrides parameter in SendEmail and SendBulkEmail to enable or disable open and click tracking for individual messages without changing your account-level or configuration set settings.

`v1.43.6`

Compare Source

`v1.43.5`

Compare Source

General Highlights

Dependency Update: Updated to the latest SDK module versions

Module Highlights

github.com/aws/aws-sdk-go-v2: v1.41.5
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/accessanalyzer: v1.45.12
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/account: v1.30.5
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/acm: v1.37.23
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/acmpca: v1.46.12
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/aiops: v1.6.21
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/amp: v1.42.9
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/amplify: v1.38.14
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/amplifybackend: v1.32.20
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/amplifyuibuilder: v1.28.20
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/apigateway: v1.39.1
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/apigatewaymanagementapi: v1.29.14
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/apigatewayv2: v1.34.1
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/appconfig: v1.43.13
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/appconfigdata: v1.23.22
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/appfabric: v1.16.21
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/appflow: v1.51.12
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/appintegrations: v1.37.7
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/applicationautoscaling: v1.41.14
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/applicationcostprofiler: v1.27.12
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/applicationdiscoveryservice: v1.35.13
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/applicationinsights: v1.34.20
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/applicationsignals: v1.19.1
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/appmesh: v1.35.12
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/apprunner: v1.39.14
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/appstream: v1.54.4
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/appsync: v1.53.5
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/arcregionswitch: v1.6.3
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/arczonalshift: v1.22.23
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/artifact: v1.15.5
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/athena: v1.57.4
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/auditmanager: v1.46.12
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/autoscaling: v1.64.4
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/autoscalingplans: v1.30.14
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/b2bi: v1.0.0-preview.100
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/backup: v1.54.11
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/backupgateway: v1.26.3
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/backupsearch: v1.6.23
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/batch: v1.63.2
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/bcmdashboards: v1.1.4
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/bcmdataexports: v1.14.0
- Feature: With this release we are providing an option to accounts to have their export delivered to an S3 bucket that is not owned by the account.
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/bcmpricingcalculator: v1.10.9
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/bcmrecommendedactions: v1.1.5
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/bedrock: v1.57.1
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/bedrockagent: v1.52.7
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/bedrockagentcore: v1.15.2
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/bedrockagentcorecontrol: v1.25.1
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/bedrockagentruntime: v1.51.8
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/bedrockdataautomation: v1.13.5
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/bedrockdataautomationruntime: v1.10.4
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the client and server clock ended up realigning.
github.com/aws/aws-sdk-go-v2/service/bedrockruntime: v1.50.4
- Bug Fix: Fix a bug where a recorded clock skew could persist on the client even if the

Configuration

📅 Schedule: (UTC)

Branch creation
- Between 12:00 AM and 03:59 AM (* 0-3 * * *)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

github-actions · 2026-04-13T02:32:43Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: 65bba25
Repo: devopsfactory-io/neptune

github-actions · 2026-04-13T02:34:56Z

🌊 Neptune Plan Results

Terraform Stacks: stack-a, stack-b

Neptune completed the plan with status: ✅

Command ✅ terraform init -input=false (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/null versions matching "~> 3.0"...
- Finding hashicorp/local versions matching "~> 2.0"...
- Installing hashicorp/null v3.2.4...
- Installed hashicorp/null v3.2.4 (signed by HashiCorp)
- Installing hashicorp/local v2.8.0...
- Installed hashicorp/local v2.8.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform init -input=false (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/null versions matching "~> 3.0"...
- Finding hashicorp/local versions matching "~> 2.0"...
- Installing hashicorp/null v3.2.4...
- Installed hashicorp/null v3.2.4 (signed by HashiCorp)
- Installing hashicorp/local v2.8.0...
- Installed hashicorp/local v2.8.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-a output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_a will be created
  + resource "null_resource" "stack_a" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-a"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-b output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_b will be created
  + resource "null_resource" "stack_b" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-b"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

To apply these changes, comment:

@neptbot apply

github-actions · 2026-04-13T02:35:01Z

🌊 Neptune Apply Results

Terraform Stacks: stack-a, stack-b

Neptune completed the apply with status: ✅

Command ✅ terraform apply -input=false tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] null_resource.stack_a: Creating...
null_resource.stack_a: Creation complete after 0s [id=1672035333654671910]
local_file.out: Creating...
local_file.out: Creation complete after 0s [id=a57cdd3e7db0022635e46b54e3ae6357944d9ed4]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

Command ✅ terraform apply -input=false tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] null_resource.stack_b: Creating...
null_resource.stack_b: Creation complete after 0s [id=1793228703302593031]
local_file.out: Creating...
local_file.out: Creation complete after 0s [id=2d8eff4b1ddeb10a7cfb78093bc91edb5b3318f8]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

github-actions · 2026-04-14T05:47:24Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: b04c298
Repo: devopsfactory-io/neptune

github-actions · 2026-04-14T05:48:14Z

🌊 Neptune Plan Results

Terraform Stacks: stack-a, stack-b

Neptune completed the plan with status: ✅

Command ✅ terraform init -input=false (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/local versions matching "~> 2.0"...
- Finding hashicorp/null versions matching "~> 3.0"...
- Installing hashicorp/null v3.2.4...
- Installed hashicorp/null v3.2.4 (signed by HashiCorp)
- Installing hashicorp/local v2.8.0...
- Installed hashicorp/local v2.8.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform init -input=false (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/local versions matching "~> 2.0"...
- Finding hashicorp/null versions matching "~> 3.0"...
- Installing hashicorp/local v2.8.0...
- Installed hashicorp/local v2.8.0 (signed by HashiCorp)
- Installing hashicorp/null v3.2.4...
- Installed hashicorp/null v3.2.4 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-a output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_a will be created
  + resource "null_resource" "stack_a" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-a"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-b output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_b will be created
  + resource "null_resource" "stack_b" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-b"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

To apply these changes, comment:

@neptbot apply

github-actions · 2026-04-14T05:48:18Z

🌊 Neptune Apply Results

Terraform Stacks: stack-a, stack-b

Neptune completed the apply with status: ✅

Command ✅ terraform apply -input=false tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] null_resource.stack_a: Creating...
null_resource.stack_a: Creation complete after 0s [id=192325180287796311]
local_file.out: Creating...
local_file.out: Creation complete after 0s [id=a57cdd3e7db0022635e46b54e3ae6357944d9ed4]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

Command ✅ terraform apply -input=false tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] null_resource.stack_b: Creating...
null_resource.stack_b: Creation complete after 0s [id=7533449980934697436]
local_file.out: Creating...
local_file.out: Creation complete after 0s [id=2d8eff4b1ddeb10a7cfb78093bc91edb5b3318f8]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

github-actions · 2026-04-21T23:52:55Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: b85da25
Repo: devopsfactory-io/neptune

github-actions · 2026-04-21T23:55:06Z

🌊 Neptune Plan Results

Terraform Stacks: stack-a, stack-b

Neptune completed the plan with status: ✅

Command ✅ terraform init -input=false (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/null versions matching "~> 3.0"...
- Finding hashicorp/local versions matching "~> 2.0"...
- Installing hashicorp/null v3.2.4...
- Installed hashicorp/null v3.2.4 (signed by HashiCorp)
- Installing hashicorp/local v2.8.0...
- Installed hashicorp/local v2.8.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform init -input=false (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/local versions matching "~> 2.0"...
- Finding hashicorp/null versions matching "~> 3.0"...
- Installing hashicorp/null v3.2.4...
- Installed hashicorp/null v3.2.4 (signed by HashiCorp)
- Installing hashicorp/local v2.8.0...
- Installed hashicorp/local v2.8.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-a output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_a will be created
  + resource "null_resource" "stack_a" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-a"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-b output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_b will be created
  + resource "null_resource" "stack_b" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-b"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

To apply these changes, comment:

@neptbot apply

github-actions · 2026-04-21T23:55:10Z

🌊 Neptune Apply Results

Terraform Stacks: stack-a, stack-b

Neptune completed the apply with status: ✅

Command ✅ terraform apply -input=false tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] null_resource.stack_a: Creating...
null_resource.stack_a: Creation complete after 0s [id=3776322936138890563]
local_file.out: Creating...
local_file.out: Creation complete after 0s [id=a57cdd3e7db0022635e46b54e3ae6357944d9ed4]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

Command ✅ terraform apply -input=false tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] null_resource.stack_b: Creating...
local_file.out: Creating...
local_file.out: Creation complete after 0s [id=2d8eff4b1ddeb10a7cfb78093bc91edb5b3318f8]
null_resource.stack_b: Creation complete after 0s [id=1181713196680866156]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

github-actions · 2026-04-22T21:35:52Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: 3d5b53c
Repo: devopsfactory-io/neptune

renovate · 2026-04-22T21:35:54Z

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

15 additional dependencies were updated

Due to Go's usage of Minimal Version Selection (MVS), these packages have been updated to the minimum version available, so will still abide by minimumReleaseAge=5 days

Details:

Package	Change
`github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream`	`v1.7.8` -> `v1.7.21`
`github.com/aws/aws-sdk-go-v2/credentials`	`v1.19.14` -> `v1.20.8`
`github.com/aws/aws-sdk-go-v2/feature/ec2/imds`	`v1.18.21` -> `v1.20.2`
`github.com/aws/aws-sdk-go-v2/internal/configsources`	`v1.4.21` -> `v1.5.5`
`github.com/aws/aws-sdk-go-v2/internal/endpoints/v2`	`v2.7.21` -> `v2.8.5`
`github.com/aws/aws-sdk-go-v2/internal/v4a`	`v1.4.22` -> `v1.5.5`
`github.com/aws/aws-sdk-go-v2/service/internal/accept-encoding`	`v1.13.7` -> `v1.13.20`
`github.com/aws/aws-sdk-go-v2/service/internal/checksum`	`v1.9.13` -> `v1.11.6`
`github.com/aws/aws-sdk-go-v2/service/internal/presigned-url`	`v1.13.21` -> `v1.14.5`
`github.com/aws/aws-sdk-go-v2/service/internal/s3shared`	`v1.19.21` -> `v1.20.5`
`github.com/aws/aws-sdk-go-v2/service/signin`	`v1.0.9` -> `v1.10.3`
`github.com/aws/aws-sdk-go-v2/service/sso`	`v1.30.15` -> `v1.38.3`
`github.com/aws/aws-sdk-go-v2/service/ssooidc`	`v1.35.19` -> `v1.43.3`
`github.com/aws/aws-sdk-go-v2/service/sts`	`v1.41.10` -> `v1.51.3`
`github.com/aws/smithy-go`	`v1.24.2` -> `v1.28.4`

File name: lambda/go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

11 additional dependencies were updated

Due to Go's usage of Minimal Version Selection (MVS), these packages have been updated to the minimum version available, so will still abide by minimumReleaseAge=5 days

Details:

Package	Change
`github.com/aws/aws-sdk-go-v2/credentials`	`v1.19.14` -> `v1.20.8`
`github.com/aws/aws-sdk-go-v2/feature/ec2/imds`	`v1.18.21` -> `v1.20.2`
`github.com/aws/aws-sdk-go-v2/internal/configsources`	`v1.4.21` -> `v1.5.5`
`github.com/aws/aws-sdk-go-v2/internal/endpoints/v2`	`v2.7.21` -> `v2.8.5`
`github.com/aws/aws-sdk-go-v2/service/internal/accept-encoding`	`v1.13.7` -> `v1.13.20`
`github.com/aws/aws-sdk-go-v2/service/internal/presigned-url`	`v1.13.21` -> `v1.14.5`
`github.com/aws/aws-sdk-go-v2/service/signin`	`v1.0.9` -> `v1.10.3`
`github.com/aws/aws-sdk-go-v2/service/sso`	`v1.30.15` -> `v1.38.3`
`github.com/aws/aws-sdk-go-v2/service/ssooidc`	`v1.35.19` -> `v1.43.3`
`github.com/aws/aws-sdk-go-v2/service/sts`	`v1.41.10` -> `v1.51.3`
`github.com/aws/smithy-go`	`v1.24.2` -> `v1.28.4`

github-actions · 2026-04-22T21:38:04Z

🌊 Neptune Plan Results

Terraform Stacks: stack-a, stack-b

Neptune completed the plan with status: ✅

Command ✅ terraform init -input=false (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/local versions matching "~> 2.0"...
- Finding hashicorp/null versions matching "~> 3.0"...
- Installing hashicorp/local v2.8.0...
- Installed hashicorp/local v2.8.0 (signed by HashiCorp)
- Installing hashicorp/null v3.2.4...
- Installed hashicorp/null v3.2.4 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform init -input=false (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/null versions matching "~> 3.0"...
- Finding hashicorp/local versions matching "~> 2.0"...
- Installing hashicorp/null v3.2.4...
- Installed hashicorp/null v3.2.4 (signed by HashiCorp)
- Installing hashicorp/local v2.8.0...
- Installed hashicorp/local v2.8.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-a output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_a will be created
  + resource "null_resource" "stack_a" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-a"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-b output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_b will be created
  + resource "null_resource" "stack_b" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-b"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

To apply these changes, comment:

@neptbot apply

github-actions · 2026-04-22T21:38:08Z

🌊 Neptune Apply Results

Terraform Stacks: stack-a, stack-b

Neptune completed the apply with status: ✅

Command ✅ terraform apply -input=false tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] local_file.out: Creating...
null_resource.stack_a: Creating...
local_file.out: Creation complete after 0s [id=a57cdd3e7db0022635e46b54e3ae6357944d9ed4]
null_resource.stack_a: Creation complete after 0s [id=3196650288103566860]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

Command ✅ terraform apply -input=false tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] null_resource.stack_b: Creating...
local_file.out: Creating...
local_file.out: Creation complete after 0s [id=2d8eff4b1ddeb10a7cfb78093bc91edb5b3318f8]
null_resource.stack_b: Creation complete after 0s [id=7428081722819201608]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

github-actions · 2026-04-23T05:05:06Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: c62a881
Repo: devopsfactory-io/neptune

github-actions · 2026-04-23T05:07:29Z

🌊 Neptune Plan Results

Terraform Stacks: stack-a, stack-b

Neptune completed the plan with status: ✅

Command ✅ terraform init -input=false (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/null versions matching "~> 3.0"...
- Finding hashicorp/local versions matching "~> 2.0"...
- Installing hashicorp/null v3.2.4...
- Installed hashicorp/null v3.2.4 (signed by HashiCorp)
- Installing hashicorp/local v2.8.0...
- Installed hashicorp/local v2.8.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform init -input=false (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/null versions matching "~> 3.0"...
- Finding hashicorp/local versions matching "~> 2.0"...
- Installing hashicorp/null v3.2.4...
- Installed hashicorp/null v3.2.4 (signed by HashiCorp)
- Installing hashicorp/local v2.8.0...
- Installed hashicorp/local v2.8.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-a output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_a will be created
  + resource "null_resource" "stack_a" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-a"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-b output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_b will be created
  + resource "null_resource" "stack_b" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-b"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

To apply these changes, comment:

@neptbot apply

github-actions · 2026-04-23T05:07:34Z

🌊 Neptune Apply Results

Terraform Stacks: stack-a, stack-b

Neptune completed the apply with status: ✅

Command ✅ terraform apply -input=false tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] local_file.out: Creating...
null_resource.stack_a: Creating...
local_file.out: Creation complete after 0s [id=a57cdd3e7db0022635e46b54e3ae6357944d9ed4]
null_resource.stack_a: Creation complete after 0s [id=3507466482357218995]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

Command ✅ terraform apply -input=false tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] null_resource.stack_b: Creating...
null_resource.stack_b: Creation complete after 0s [id=8765085218958696063]
local_file.out: Creating...
local_file.out: Creation complete after 0s [id=2d8eff4b1ddeb10a7cfb78093bc91edb5b3318f8]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

github-actions · 2026-04-23T09:09:12Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: 6825aa6
Repo: devopsfactory-io/neptune

github-actions · 2026-09-06T01:00:07Z

🌊 Neptune Plan Results

Terraform Stacks: stack-a, stack-b

Neptune completed the plan with status: ✅

Command ✅ terraform init -input=false (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/null versions matching "~> 3.0"...
- Finding hashicorp/local versions matching "~> 2.0"...
- Installing hashicorp/null v3.3.1...
- Installed hashicorp/null v3.3.1 (signed by HashiCorp)
- Installing hashicorp/local v2.9.0...
- Installed hashicorp/local v2.9.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform init -input=false (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/local versions matching "~> 2.0"...
- Finding hashicorp/null versions matching "~> 3.0"...
- Installing hashicorp/local v2.9.0...
- Installed hashicorp/local v2.9.0 (signed by HashiCorp)
- Installing hashicorp/null v3.3.1...
- Installed hashicorp/null v3.3.1 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-a output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_a will be created
  + resource "null_resource" "stack_a" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-a"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-b output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_b will be created
  + resource "null_resource" "stack_b" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-b"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

To apply these changes, comment:

@neptbot apply

github-actions · 2026-09-06T01:00:12Z

🌊 Neptune Apply Results

Terraform Stacks: stack-a, stack-b

Neptune completed the apply with status: ✅

Command ✅ terraform apply -input=false tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] null_resource.stack_a: Creating...
local_file.out: Creating...
null_resource.stack_a: Creation complete after 0s [id=1729325202596409303]
local_file.out: Creation complete after 0s [id=a57cdd3e7db0022635e46b54e3ae6357944d9ed4]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

Command ✅ terraform apply -input=false tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] null_resource.stack_b: Creating...
local_file.out: Creating...
null_resource.stack_b: Creation complete after 0s [id=3527274522693145026]
local_file.out: Creation complete after 0s [id=2d8eff4b1ddeb10a7cfb78093bc91edb5b3318f8]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

github-actions · 2026-09-09T21:49:08Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: 9ed00e9
Repo: devopsfactory-io/neptune

coderabbitai · 2026-09-09T21:49:09Z

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults
Review profile: CHILL
Plan: Advanced
Run ID: 44c5b89b-c740-43ef-bfe1-cc7fc02f3bb8

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

github-actions · 2026-09-09T21:51:34Z

🌊 Neptune Plan Results

Terraform Stacks: stack-a, stack-b

Neptune completed the plan with status: ✅

Command ✅ terraform init -input=false (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/local versions matching "~> 2.0"...
- Finding hashicorp/null versions matching "~> 3.0"...
- Installing hashicorp/local v2.9.0...
- Installed hashicorp/local v2.9.0 (signed by HashiCorp)
- Installing hashicorp/null v3.3.1...
- Installed hashicorp/null v3.3.1 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform init -input=false (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/null versions matching "~> 3.0"...
- Finding hashicorp/local versions matching "~> 2.0"...
- Installing hashicorp/local v2.9.0...
- Installed hashicorp/local v2.9.0 (signed by HashiCorp)
- Installing hashicorp/null v3.3.1...
- Installed hashicorp/null v3.3.1 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-a output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_a will be created
  + resource "null_resource" "stack_a" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-a"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

Command ✅ terraform plan -input=false -out=tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # local_file.out will be created
  + resource "local_file" "out" {
      + content              = "stack-b output"
      + content_base64sha256 = (known after apply)
      + content_base64sha512 = (known after apply)
      + content_md5          = (known after apply)
      + content_sha1         = (known after apply)
      + content_sha256       = (known after apply)
      + content_sha512       = (known after apply)
      + directory_permission = "0777"
      + file_permission      = "0777"
      + filename             = "./out.txt"
      + id                   = (known after apply)
    }

  # null_resource.stack_b will be created
  + resource "null_resource" "stack_b" {
      + id       = (known after apply)
      + triggers = {
          + "stack" = "stack-b"
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

To apply these changes, comment:

@neptbot apply

github-actions · 2026-09-09T21:51:40Z

🌊 Neptune Apply Results

Terraform Stacks: stack-a, stack-b

Neptune completed the apply with status: ✅

Command ✅ terraform apply -input=false tfplan (stack: stack-a)

Click to see the command output

stderr:


stdout:
[stack-a] local_file.out: Creating...
local_file.out: Creation complete after 0s [id=a57cdd3e7db0022635e46b54e3ae6357944d9ed4]
null_resource.stack_a: Creating...
null_resource.stack_a: Creation complete after 0s [id=4663400443007980862]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

Command ✅ terraform apply -input=false tfplan (stack: stack-b)

Click to see the command output

stderr:


stdout:
[stack-b] local_file.out: Creating...
null_resource.stack_b: Creating...
local_file.out: Creation complete after 0s [id=2d8eff4b1ddeb10a7cfb78093bc91edb5b3318f8]
null_resource.stack_b: Creation complete after 0s [id=4986777761883698102]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

github-actions · 2026-09-13T21:33:31Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: 53f94ba
Repo: devopsfactory-io/neptune

github-actions · 2026-09-14T18:52:50Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: b7aad60
Repo: devopsfactory-io/neptune

github-actions · 2026-09-16T19:07:07Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: 72b9e69
Repo: devopsfactory-io/neptune

github-actions · 2026-09-19T21:56:08Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: 607f070
Repo: devopsfactory-io/neptune

github-actions · 2026-09-20T22:59:21Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: 41d059f
Repo: devopsfactory-io/neptune

github-actions · 2026-09-26T22:57:43Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: 64fc0ad
Repo: devopsfactory-io/neptune

github-actions · 2026-09-28T21:26:29Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: 46ee89c
Repo: devopsfactory-io/neptune

github-actions · 2026-09-29T18:52:15Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: ef5c227
Repo: devopsfactory-io/neptune

github-actions · 2026-10-12T02:00:49Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: 838c769
Repo: devopsfactory-io/neptune

github-actions · 2026-10-13T20:14:27Z

Lambda integration test executed with success...

client_payload:

PR: fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) #131
Branch: renovate/main-aws-sdk-go-v2-monorepo
Command: plan
SHA: 4bbd4fc
Repo: devopsfactory-io/neptune

renovate Bot added the dependencies label Apr 13, 2026

github-actions Bot added the neptune label Apr 13, 2026

neptune-ci-tests Bot mentioned this pull request Apr 13, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#91

Closed

renovate Bot force-pushed the renovate/main-aws-sdk-go-v2-monorepo branch from 65bba25 to b04c298 Compare April 14, 2026 05:47

neptune-ci-tests Bot mentioned this pull request Apr 14, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#94

Closed

renovate Bot force-pushed the renovate/main-aws-sdk-go-v2-monorepo branch from b04c298 to b85da25 Compare April 21, 2026 23:52

renovate Bot changed the title ~~fix(deps): update module github.com/aws/aws-sdk-go-v2/service/s3 to v1.99.0 in go.mod (main)~~ fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod (main) Apr 21, 2026

neptune-ci-tests Bot mentioned this pull request Apr 21, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#102

Closed

renovate Bot force-pushed the renovate/main-aws-sdk-go-v2-monorepo branch from b85da25 to 3d5b53c Compare April 22, 2026 21:35

neptune-ci-tests Bot mentioned this pull request Apr 22, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#104

Closed

renovate Bot force-pushed the renovate/main-aws-sdk-go-v2-monorepo branch from 3d5b53c to c62a881 Compare April 23, 2026 05:04

neptune-ci-tests Bot mentioned this pull request Apr 23, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#105

Closed

renovate Bot force-pushed the renovate/main-aws-sdk-go-v2-monorepo branch from c62a881 to 6825aa6 Compare April 23, 2026 09:09

neptune-ci-tests Bot mentioned this pull request Sep 6, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#275

Closed

neptune-ci-tests Bot mentioned this pull request Sep 9, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#276

Closed

neptune-ci-tests Bot mentioned this pull request Sep 13, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#277

Closed

neptune-ci-tests Bot mentioned this pull request Sep 14, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#278

Closed

neptune-ci-tests Bot mentioned this pull request Sep 16, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#279

Closed

neptune-ci-tests Bot mentioned this pull request Sep 19, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#280

Closed

neptune-ci-tests Bot mentioned this pull request Sep 20, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#281

Closed

neptune-ci-tests Bot mentioned this pull request Sep 26, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#302

Closed

neptune-ci-tests Bot mentioned this pull request Sep 28, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#303

Closed

This was referenced Sep 29, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#304

Closed

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#305

Closed

neptune-ci-tests Bot mentioned this pull request Oct 12, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#308

Closed

fix(deps): update aws-sdk-go-v2 monorepo in lambda/go.mod

4bbd4fc

neptune-ci-tests Bot mentioned this pull request Oct 13, 2026

CI: Neptune PR #131 integration test devopsfactory-io/neptune-tests#309

Closed

Conversation

renovate Bot commented Apr 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Module Highlights

Module Highlights

General Highlights

Module Highlights

Module Highlights

General Highlights

Module Highlights

Module Highlights

Module Highlights

General Highlights

Module Highlights

General Highlights

Module Highlights

General Highlights

Module Highlights

Configuration

Uh oh!

github-actions Bot commented Apr 13, 2026

Uh oh!

github-actions Bot commented Apr 13, 2026

🌊 Neptune Plan Results

Uh oh!

github-actions Bot commented Apr 13, 2026

🌊 Neptune Apply Results

Uh oh!

github-actions Bot commented Apr 14, 2026

Uh oh!

github-actions Bot commented Apr 14, 2026

🌊 Neptune Plan Results

Uh oh!

github-actions Bot commented Apr 14, 2026

🌊 Neptune Apply Results

Uh oh!

github-actions Bot commented Apr 21, 2026

Uh oh!

github-actions Bot commented Apr 21, 2026

🌊 Neptune Plan Results

Uh oh!

github-actions Bot commented Apr 21, 2026

🌊 Neptune Apply Results

Uh oh!

github-actions Bot commented Apr 22, 2026

Uh oh!

renovate Bot commented Apr 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

ℹ️ Artifact update notice

File name: go.mod

File name: lambda/go.mod

Uh oh!

github-actions Bot commented Apr 22, 2026

🌊 Neptune Plan Results

Uh oh!

github-actions Bot commented Apr 22, 2026

🌊 Neptune Apply Results

Uh oh!

github-actions Bot commented Apr 23, 2026

Uh oh!

github-actions Bot commented Apr 23, 2026

🌊 Neptune Plan Results

Uh oh!

github-actions Bot commented Apr 23, 2026

🌊 Neptune Apply Results

Uh oh!

github-actions Bot commented Apr 23, 2026

Uh oh!

github-actions Bot commented Sep 6, 2026

🌊 Neptune Plan Results

Uh oh!

github-actions Bot commented Sep 6, 2026

🌊 Neptune Apply Results

Uh oh!

github-actions Bot commented Sep 9, 2026

Uh oh!

coderabbitai Bot commented Sep 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

renovate Bot commented Apr 13, 2026 •

edited

Loading

renovate Bot commented Apr 22, 2026 •

edited

Loading

coderabbitai Bot commented Sep 9, 2026 •

edited

Loading