Php App Layer Args
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as aws from "@pulumi/aws";
const app = new aws.opsworks.PhpAppLayer("app", {stackId: main.id});
import pulumi
import pulumi_aws as aws
app = aws.opsworks.PhpAppLayer("app", stack_id=main["id"])
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Aws = Pulumi.Aws;
return await Deployment.RunAsync(() =>
{
var app = new Aws.OpsWorks.PhpAppLayer("app", new()
{
StackId = main.Id,
});
});
package main
import (
"github.com/pulumi/pulumi-aws/sdk/v6/go/aws/opsworks"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
_, err := opsworks.NewPhpAppLayer(ctx, "app", &opsworks.PhpAppLayerArgs{
StackId: pulumi.Any(main.Id),
})
if err != nil {
return err
}
return nil
})
}
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.aws.opsworks.PhpAppLayer;
import com.pulumi.aws.opsworks.PhpAppLayerArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
var app = new PhpAppLayer("app", PhpAppLayerArgs.builder()
.stackId(main.id())
.build());
}
}
resources:
app:
type: aws:opsworks:PhpAppLayer
properties:
stackId: ${main.id}
Import
Using pulumi import
, import OpsWorks PHP Application Layers using the id
. For example:
$ pulumi import aws:opsworks/phpAppLayer:PhpAppLayer bar 00000000-0000-0000-0000-000000000000
Constructors
Properties
Whether to automatically assign an elastic IP address to the layer's instances.
For stacks belonging to a VPC, whether to automatically assign a public IP address to each of the layer's instances.
Whether to enable auto-healing for the layer.
The ARN of an IAM profile that will be used for the layer's instances.
Custom JSON attributes to apply to the layer.
Ids for a set of security groups to apply to the layer's instances.
Whether to enable Elastic Load Balancing connection draining.
ebs_volume
blocks, as described below, will each create an EBS volume and connect it to the layer's instances.
Name of an Elastic Load Balancer to attach to this layer
Whether to install OS and package updates on each instance when it boots.
The time, in seconds, that OpsWorks will wait for Chef to complete after triggering the Shutdown event.
Names of a set of system packages to install on the layer's instances.
A map of tags to assign to the resource. .If configured with a provider default_tags
configuration block present, tags with matching keys will overwrite those defined at the provider-level. The following extra optional arguments, all lists of Chef recipe names, allow custom Chef recipes to be applied to layer instances at the five different lifecycle events, if custom cookbooks are enabled on the layer's stack:
Whether to use EBS-optimized instances.