2022-04-19 16:39:23 +00:00
|
|
|
// Code generated by test DO NOT EDIT.
|
|
|
|
// *** WARNING: Do not edit by hand unless you're certain you know what you are doing! ***
|
2021-09-22 03:48:45 +00:00
|
|
|
|
|
|
|
package example
|
|
|
|
|
|
|
|
import (
|
|
|
|
"context"
|
|
|
|
"reflect"
|
|
|
|
|
|
|
|
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
|
2023-06-14 16:34:49 +00:00
|
|
|
"resource-args-python-case-insensitive/example/internal"
|
2021-09-22 03:48:45 +00:00
|
|
|
)
|
|
|
|
|
|
|
|
type Pet struct {
|
|
|
|
pulumi.CustomResourceState
|
|
|
|
|
|
|
|
Name pulumi.StringPtrOutput `pulumi:"name"`
|
|
|
|
}
|
|
|
|
|
|
|
|
// NewPet registers a new resource with the given unique name, arguments, and options.
|
|
|
|
func NewPet(ctx *pulumi.Context,
|
|
|
|
name string, args *PetArgs, opts ...pulumi.ResourceOption) (*Pet, error) {
|
|
|
|
if args == nil {
|
|
|
|
args = &PetArgs{}
|
|
|
|
}
|
|
|
|
|
2023-06-14 16:34:49 +00:00
|
|
|
opts = internal.PkgResourceDefaultOpts(opts)
|
2021-09-22 03:48:45 +00:00
|
|
|
var resource Pet
|
|
|
|
err := ctx.RegisterResource("example::Pet", name, args, &resource, opts...)
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
return &resource, nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// GetPet gets an existing Pet resource's state with the given name, ID, and optional
|
|
|
|
// state properties that are used to uniquely qualify the lookup (nil if not required).
|
|
|
|
func GetPet(ctx *pulumi.Context,
|
|
|
|
name string, id pulumi.IDInput, state *PetState, opts ...pulumi.ResourceOption) (*Pet, error) {
|
|
|
|
var resource Pet
|
|
|
|
err := ctx.ReadResource("example::Pet", name, id, state, &resource, opts...)
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
return &resource, nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// Input properties used for looking up and filtering Pet resources.
|
|
|
|
type petState struct {
|
|
|
|
}
|
|
|
|
|
|
|
|
type PetState struct {
|
|
|
|
}
|
|
|
|
|
|
|
|
func (PetState) ElementType() reflect.Type {
|
|
|
|
return reflect.TypeOf((*petState)(nil)).Elem()
|
|
|
|
}
|
|
|
|
|
|
|
|
type petArgs struct {
|
|
|
|
Name *string `pulumi:"name"`
|
|
|
|
}
|
|
|
|
|
|
|
|
// The set of arguments for constructing a Pet resource.
|
|
|
|
type PetArgs struct {
|
|
|
|
Name pulumi.StringPtrInput
|
|
|
|
}
|
|
|
|
|
|
|
|
func (PetArgs) ElementType() reflect.Type {
|
|
|
|
return reflect.TypeOf((*petArgs)(nil)).Elem()
|
|
|
|
}
|
|
|
|
|
|
|
|
type PetInput interface {
|
|
|
|
pulumi.Input
|
|
|
|
|
|
|
|
ToPetOutput() PetOutput
|
|
|
|
ToPetOutputWithContext(ctx context.Context) PetOutput
|
|
|
|
}
|
|
|
|
|
|
|
|
func (*Pet) ElementType() reflect.Type {
|
[codegen/go] Remove ResourcePtr input/output types (#8449)
These changes remove the `Ptr` variants of input/ouptut types for
resources. A `TPtr` input or output is normally generated for `T` if `T`
is present in an `optional(input(T))` or `optional(output(T))` and if
the Go representation for `T` is not nilable. The generation of `Ptr`
variants for resource types breaks the latter rule: the canonical
representation of a resource type named `Foo` is a pointer to a struct
type named `Foo` (i.e. `*Foo`). `Foo` itself is not a resource, as it
does not implement the Go `Resource` interface. Because this
representation already accommodates `nil` to indicate the lack of a
value, we need not generate `FooPtr{Input,Output}` types.
Besides being unnecessary, the implementation of `Ptr` types for
resources was incorrect. Rather than using `**Foo` as their element
type, these types use `*Foo`--identical to the element type used for
the normal input/output types. Furthermore, the generated code for
at least `FooOutput.ToFooPtrOutputWithContext` and `FooPtrOutput.Elem`
was incorrect, making these types virtually unusable in practice.
Finally, these `Ptr` types should never appear on input/output
properties in practice, as the logic we use to generate input and output
type references never generates them for `optional({input,output}(T)).
Instead, it generates references to the standard input/output types.
Though this is _technically_ a breaking change--it changes the set of
exported types for any package that defines resources--I believe that in
practice it will be invisible to users for the reasons stated above.
These types are not usable, and were never referenced.
This is preparatory work for #7943.
2021-11-23 18:24:56 +00:00
|
|
|
return reflect.TypeOf((**Pet)(nil)).Elem()
|
2021-09-22 03:48:45 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
func (i *Pet) ToPetOutput() PetOutput {
|
|
|
|
return i.ToPetOutputWithContext(context.Background())
|
|
|
|
}
|
|
|
|
|
|
|
|
func (i *Pet) ToPetOutputWithContext(ctx context.Context) PetOutput {
|
|
|
|
return pulumi.ToOutputWithContext(ctx, i).(PetOutput)
|
|
|
|
}
|
|
|
|
|
|
|
|
// PetArrayInput is an input type that accepts PetArray and PetArrayOutput values.
|
|
|
|
// You can construct a concrete instance of `PetArrayInput` via:
|
|
|
|
//
|
2022-09-14 02:12:02 +00:00
|
|
|
// PetArray{ PetArgs{...} }
|
2021-09-22 03:48:45 +00:00
|
|
|
type PetArrayInput interface {
|
|
|
|
pulumi.Input
|
|
|
|
|
|
|
|
ToPetArrayOutput() PetArrayOutput
|
|
|
|
ToPetArrayOutputWithContext(context.Context) PetArrayOutput
|
|
|
|
}
|
|
|
|
|
|
|
|
type PetArray []PetInput
|
|
|
|
|
|
|
|
func (PetArray) ElementType() reflect.Type {
|
|
|
|
return reflect.TypeOf((*[]*Pet)(nil)).Elem()
|
|
|
|
}
|
|
|
|
|
|
|
|
func (i PetArray) ToPetArrayOutput() PetArrayOutput {
|
|
|
|
return i.ToPetArrayOutputWithContext(context.Background())
|
|
|
|
}
|
|
|
|
|
|
|
|
func (i PetArray) ToPetArrayOutputWithContext(ctx context.Context) PetArrayOutput {
|
|
|
|
return pulumi.ToOutputWithContext(ctx, i).(PetArrayOutput)
|
|
|
|
}
|
|
|
|
|
|
|
|
// PetMapInput is an input type that accepts PetMap and PetMapOutput values.
|
|
|
|
// You can construct a concrete instance of `PetMapInput` via:
|
|
|
|
//
|
2022-09-14 02:12:02 +00:00
|
|
|
// PetMap{ "key": PetArgs{...} }
|
2021-09-22 03:48:45 +00:00
|
|
|
type PetMapInput interface {
|
|
|
|
pulumi.Input
|
|
|
|
|
|
|
|
ToPetMapOutput() PetMapOutput
|
|
|
|
ToPetMapOutputWithContext(context.Context) PetMapOutput
|
|
|
|
}
|
|
|
|
|
|
|
|
type PetMap map[string]PetInput
|
|
|
|
|
|
|
|
func (PetMap) ElementType() reflect.Type {
|
|
|
|
return reflect.TypeOf((*map[string]*Pet)(nil)).Elem()
|
|
|
|
}
|
|
|
|
|
|
|
|
func (i PetMap) ToPetMapOutput() PetMapOutput {
|
|
|
|
return i.ToPetMapOutputWithContext(context.Background())
|
|
|
|
}
|
|
|
|
|
|
|
|
func (i PetMap) ToPetMapOutputWithContext(ctx context.Context) PetMapOutput {
|
|
|
|
return pulumi.ToOutputWithContext(ctx, i).(PetMapOutput)
|
|
|
|
}
|
|
|
|
|
|
|
|
type PetOutput struct{ *pulumi.OutputState }
|
|
|
|
|
|
|
|
func (PetOutput) ElementType() reflect.Type {
|
[codegen/go] Remove ResourcePtr input/output types (#8449)
These changes remove the `Ptr` variants of input/ouptut types for
resources. A `TPtr` input or output is normally generated for `T` if `T`
is present in an `optional(input(T))` or `optional(output(T))` and if
the Go representation for `T` is not nilable. The generation of `Ptr`
variants for resource types breaks the latter rule: the canonical
representation of a resource type named `Foo` is a pointer to a struct
type named `Foo` (i.e. `*Foo`). `Foo` itself is not a resource, as it
does not implement the Go `Resource` interface. Because this
representation already accommodates `nil` to indicate the lack of a
value, we need not generate `FooPtr{Input,Output}` types.
Besides being unnecessary, the implementation of `Ptr` types for
resources was incorrect. Rather than using `**Foo` as their element
type, these types use `*Foo`--identical to the element type used for
the normal input/output types. Furthermore, the generated code for
at least `FooOutput.ToFooPtrOutputWithContext` and `FooPtrOutput.Elem`
was incorrect, making these types virtually unusable in practice.
Finally, these `Ptr` types should never appear on input/output
properties in practice, as the logic we use to generate input and output
type references never generates them for `optional({input,output}(T)).
Instead, it generates references to the standard input/output types.
Though this is _technically_ a breaking change--it changes the set of
exported types for any package that defines resources--I believe that in
practice it will be invisible to users for the reasons stated above.
These types are not usable, and were never referenced.
This is preparatory work for #7943.
2021-11-23 18:24:56 +00:00
|
|
|
return reflect.TypeOf((**Pet)(nil)).Elem()
|
2021-09-22 03:48:45 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
func (o PetOutput) ToPetOutput() PetOutput {
|
|
|
|
return o
|
|
|
|
}
|
|
|
|
|
|
|
|
func (o PetOutput) ToPetOutputWithContext(ctx context.Context) PetOutput {
|
|
|
|
return o
|
|
|
|
}
|
|
|
|
|
2022-05-03 18:36:57 +00:00
|
|
|
func (o PetOutput) Name() pulumi.StringPtrOutput {
|
|
|
|
return o.ApplyT(func(v *Pet) pulumi.StringPtrOutput { return v.Name }).(pulumi.StringPtrOutput)
|
|
|
|
}
|
|
|
|
|
2021-09-22 03:48:45 +00:00
|
|
|
type PetArrayOutput struct{ *pulumi.OutputState }
|
|
|
|
|
|
|
|
func (PetArrayOutput) ElementType() reflect.Type {
|
[codegen/go] Remove ResourcePtr input/output types (#8449)
These changes remove the `Ptr` variants of input/ouptut types for
resources. A `TPtr` input or output is normally generated for `T` if `T`
is present in an `optional(input(T))` or `optional(output(T))` and if
the Go representation for `T` is not nilable. The generation of `Ptr`
variants for resource types breaks the latter rule: the canonical
representation of a resource type named `Foo` is a pointer to a struct
type named `Foo` (i.e. `*Foo`). `Foo` itself is not a resource, as it
does not implement the Go `Resource` interface. Because this
representation already accommodates `nil` to indicate the lack of a
value, we need not generate `FooPtr{Input,Output}` types.
Besides being unnecessary, the implementation of `Ptr` types for
resources was incorrect. Rather than using `**Foo` as their element
type, these types use `*Foo`--identical to the element type used for
the normal input/output types. Furthermore, the generated code for
at least `FooOutput.ToFooPtrOutputWithContext` and `FooPtrOutput.Elem`
was incorrect, making these types virtually unusable in practice.
Finally, these `Ptr` types should never appear on input/output
properties in practice, as the logic we use to generate input and output
type references never generates them for `optional({input,output}(T)).
Instead, it generates references to the standard input/output types.
Though this is _technically_ a breaking change--it changes the set of
exported types for any package that defines resources--I believe that in
practice it will be invisible to users for the reasons stated above.
These types are not usable, and were never referenced.
This is preparatory work for #7943.
2021-11-23 18:24:56 +00:00
|
|
|
return reflect.TypeOf((*[]*Pet)(nil)).Elem()
|
2021-09-22 03:48:45 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
func (o PetArrayOutput) ToPetArrayOutput() PetArrayOutput {
|
|
|
|
return o
|
|
|
|
}
|
|
|
|
|
|
|
|
func (o PetArrayOutput) ToPetArrayOutputWithContext(ctx context.Context) PetArrayOutput {
|
|
|
|
return o
|
|
|
|
}
|
|
|
|
|
|
|
|
func (o PetArrayOutput) Index(i pulumi.IntInput) PetOutput {
|
[codegen/go] Remove ResourcePtr input/output types (#8449)
These changes remove the `Ptr` variants of input/ouptut types for
resources. A `TPtr` input or output is normally generated for `T` if `T`
is present in an `optional(input(T))` or `optional(output(T))` and if
the Go representation for `T` is not nilable. The generation of `Ptr`
variants for resource types breaks the latter rule: the canonical
representation of a resource type named `Foo` is a pointer to a struct
type named `Foo` (i.e. `*Foo`). `Foo` itself is not a resource, as it
does not implement the Go `Resource` interface. Because this
representation already accommodates `nil` to indicate the lack of a
value, we need not generate `FooPtr{Input,Output}` types.
Besides being unnecessary, the implementation of `Ptr` types for
resources was incorrect. Rather than using `**Foo` as their element
type, these types use `*Foo`--identical to the element type used for
the normal input/output types. Furthermore, the generated code for
at least `FooOutput.ToFooPtrOutputWithContext` and `FooPtrOutput.Elem`
was incorrect, making these types virtually unusable in practice.
Finally, these `Ptr` types should never appear on input/output
properties in practice, as the logic we use to generate input and output
type references never generates them for `optional({input,output}(T)).
Instead, it generates references to the standard input/output types.
Though this is _technically_ a breaking change--it changes the set of
exported types for any package that defines resources--I believe that in
practice it will be invisible to users for the reasons stated above.
These types are not usable, and were never referenced.
This is preparatory work for #7943.
2021-11-23 18:24:56 +00:00
|
|
|
return pulumi.All(o, i).ApplyT(func(vs []interface{}) *Pet {
|
|
|
|
return vs[0].([]*Pet)[vs[1].(int)]
|
2021-09-22 03:48:45 +00:00
|
|
|
}).(PetOutput)
|
|
|
|
}
|
|
|
|
|
|
|
|
type PetMapOutput struct{ *pulumi.OutputState }
|
|
|
|
|
|
|
|
func (PetMapOutput) ElementType() reflect.Type {
|
[codegen/go] Remove ResourcePtr input/output types (#8449)
These changes remove the `Ptr` variants of input/ouptut types for
resources. A `TPtr` input or output is normally generated for `T` if `T`
is present in an `optional(input(T))` or `optional(output(T))` and if
the Go representation for `T` is not nilable. The generation of `Ptr`
variants for resource types breaks the latter rule: the canonical
representation of a resource type named `Foo` is a pointer to a struct
type named `Foo` (i.e. `*Foo`). `Foo` itself is not a resource, as it
does not implement the Go `Resource` interface. Because this
representation already accommodates `nil` to indicate the lack of a
value, we need not generate `FooPtr{Input,Output}` types.
Besides being unnecessary, the implementation of `Ptr` types for
resources was incorrect. Rather than using `**Foo` as their element
type, these types use `*Foo`--identical to the element type used for
the normal input/output types. Furthermore, the generated code for
at least `FooOutput.ToFooPtrOutputWithContext` and `FooPtrOutput.Elem`
was incorrect, making these types virtually unusable in practice.
Finally, these `Ptr` types should never appear on input/output
properties in practice, as the logic we use to generate input and output
type references never generates them for `optional({input,output}(T)).
Instead, it generates references to the standard input/output types.
Though this is _technically_ a breaking change--it changes the set of
exported types for any package that defines resources--I believe that in
practice it will be invisible to users for the reasons stated above.
These types are not usable, and were never referenced.
This is preparatory work for #7943.
2021-11-23 18:24:56 +00:00
|
|
|
return reflect.TypeOf((*map[string]*Pet)(nil)).Elem()
|
2021-09-22 03:48:45 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
func (o PetMapOutput) ToPetMapOutput() PetMapOutput {
|
|
|
|
return o
|
|
|
|
}
|
|
|
|
|
|
|
|
func (o PetMapOutput) ToPetMapOutputWithContext(ctx context.Context) PetMapOutput {
|
|
|
|
return o
|
|
|
|
}
|
|
|
|
|
|
|
|
func (o PetMapOutput) MapIndex(k pulumi.StringInput) PetOutput {
|
[codegen/go] Remove ResourcePtr input/output types (#8449)
These changes remove the `Ptr` variants of input/ouptut types for
resources. A `TPtr` input or output is normally generated for `T` if `T`
is present in an `optional(input(T))` or `optional(output(T))` and if
the Go representation for `T` is not nilable. The generation of `Ptr`
variants for resource types breaks the latter rule: the canonical
representation of a resource type named `Foo` is a pointer to a struct
type named `Foo` (i.e. `*Foo`). `Foo` itself is not a resource, as it
does not implement the Go `Resource` interface. Because this
representation already accommodates `nil` to indicate the lack of a
value, we need not generate `FooPtr{Input,Output}` types.
Besides being unnecessary, the implementation of `Ptr` types for
resources was incorrect. Rather than using `**Foo` as their element
type, these types use `*Foo`--identical to the element type used for
the normal input/output types. Furthermore, the generated code for
at least `FooOutput.ToFooPtrOutputWithContext` and `FooPtrOutput.Elem`
was incorrect, making these types virtually unusable in practice.
Finally, these `Ptr` types should never appear on input/output
properties in practice, as the logic we use to generate input and output
type references never generates them for `optional({input,output}(T)).
Instead, it generates references to the standard input/output types.
Though this is _technically_ a breaking change--it changes the set of
exported types for any package that defines resources--I believe that in
practice it will be invisible to users for the reasons stated above.
These types are not usable, and were never referenced.
This is preparatory work for #7943.
2021-11-23 18:24:56 +00:00
|
|
|
return pulumi.All(o, k).ApplyT(func(vs []interface{}) *Pet {
|
|
|
|
return vs[0].(map[string]*Pet)[vs[1].(string)]
|
2021-09-22 03:48:45 +00:00
|
|
|
}).(PetOutput)
|
|
|
|
}
|
|
|
|
|
|
|
|
func init() {
|
2021-10-14 17:41:40 +00:00
|
|
|
pulumi.RegisterInputType(reflect.TypeOf((*PetInput)(nil)).Elem(), &Pet{})
|
|
|
|
pulumi.RegisterInputType(reflect.TypeOf((*PetArrayInput)(nil)).Elem(), PetArray{})
|
|
|
|
pulumi.RegisterInputType(reflect.TypeOf((*PetMapInput)(nil)).Elem(), PetMap{})
|
2021-09-22 03:48:45 +00:00
|
|
|
pulumi.RegisterOutputType(PetOutput{})
|
|
|
|
pulumi.RegisterOutputType(PetArrayOutput{})
|
|
|
|
pulumi.RegisterOutputType(PetMapOutput{})
|
|
|
|
}
|