8c5a9ac033
Fixes: #497
This PR follows the `weekly-pulumi-update` CI workflow steps to update
our `pulumi/pulumi` dependency, with manual intervention to resolve
tooling update conflicts. Before generating the SDKs, it's necessary to
update the language tools and otel packages to ensure compatibility with
the latest changes.
Additional command executed for the manual updates:
```sh
TOOLS=(
"github.com/pulumi/pulumi/sdk/go/pulumi-language-go/v3"
"github.com/pulumi/pulumi/sdk/nodejs/cmd/pulumi-language-nodejs/v3"
"github.com/pulumi/pulumi/sdk/python/cmd/pulumi-language-python/v3"
"go.opentelemetry.io/otel/exporters/otlp/otlptrace"
)
for TOOL in "${TOOLS[@]}"; do
go get -u $TOOL
go mod tidy
done
```
---
Note: the Go directive is upgraded to v1.24 as
`github.com/pulumi/pulumi/sdk/go/pulumi-language-go/v3` requires Go
v1.24
([ref](5c96e4e6aa/sdk/go/pulumi-language-go/go.mod (L3))).
51 lines
1.6 KiB
C#
Generated
51 lines
1.6 KiB
C#
Generated
// *** WARNING: this file was generated by pulumi-language-dotnet. ***
|
|
// *** Do not edit by hand unless you're certain you know what you are doing! ***
|
|
|
|
using System;
|
|
using System.Collections.Generic;
|
|
using System.Collections.Immutable;
|
|
using System.Threading.Tasks;
|
|
using Pulumi.Serialization;
|
|
|
|
namespace Pulumi.DockerBuild.Inputs
|
|
{
|
|
|
|
public sealed class BuildContextArgs : global::Pulumi.ResourceArgs
|
|
{
|
|
/// <summary>
|
|
/// Resources to use for build context.
|
|
///
|
|
/// The location can be:
|
|
/// * A relative or absolute path to a local directory (`.`, `./app`,
|
|
/// `/app`, etc.).
|
|
/// * A remote URL of a Git repository, tarball, or plain text file
|
|
/// (`https://github.com/user/myrepo.git`, `http://server/context.tar.gz`,
|
|
/// etc.).
|
|
/// </summary>
|
|
[Input("location", required: true)]
|
|
public Input<string> Location { get; set; } = null!;
|
|
|
|
[Input("named")]
|
|
private InputMap<Inputs.ContextArgs>? _named;
|
|
|
|
/// <summary>
|
|
/// Additional build contexts to use.
|
|
///
|
|
/// These contexts are accessed with `FROM name` or `--from=name`
|
|
/// statements when using Dockerfile 1.4+ syntax.
|
|
///
|
|
/// Values can be local paths, HTTP URLs, or `docker-image://` images.
|
|
/// </summary>
|
|
public InputMap<Inputs.ContextArgs> Named
|
|
{
|
|
get => _named ?? (_named = new InputMap<Inputs.ContextArgs>());
|
|
set => _named = value;
|
|
}
|
|
|
|
public BuildContextArgs()
|
|
{
|
|
}
|
|
public static new BuildContextArgs Empty => new BuildContextArgs();
|
|
}
|
|
}
|