@pulumi/databricks
Version:
A Pulumi package for creating and managing databricks cloud resources.
86 lines • 4.15 kB
JavaScript
;
// *** WARNING: this file was generated by the Pulumi Terraform Bridge (tfgen) Tool. ***
// *** Do not edit by hand unless you're certain you know what you are doing! ***
Object.defineProperty(exports, "__esModule", { value: true });
exports.getAwsCrossAccountPolicyOutput = exports.getAwsCrossAccountPolicy = void 0;
const pulumi = require("@pulumi/pulumi");
const utilities = require("./utilities");
/**
* > **Note** This data source can only be used with an account-level provider!
*
* This data source constructs necessary AWS cross-account policy for you, which is based on [official documentation](https://docs.databricks.com/administration-guide/account-api/iam-role.html#language-Your%C2%A0VPC,%C2%A0default).
*
* ## Example Usage
*
* For more detailed usage please see databricks.getAwsAssumeRolePolicy or databricksAwsS3Mount pages.
*
* ```typescript
* import * as pulumi from "@pulumi/pulumi";
* import * as databricks from "@pulumi/databricks";
*
* const _this = databricks.getAwsCrossAccountPolicy({});
* ```
*
* ## Related Resources
*
* The following resources are used in the same context:
*
* * Provisioning AWS Databricks workspaces with a Hub & Spoke firewall for data exfiltration protection guide
* * databricks.getAwsAssumeRolePolicy data to construct the necessary AWS STS assume role policy.
* * databricks.getAwsBucketPolicy data to configure a simple access policy for AWS S3 buckets, so that Databricks can access data in it.
* * databricks.InstanceProfile to manage AWS EC2 instance profiles that users can launch databricks.Cluster and access data, like databricks_mount.
*/
function getAwsCrossAccountPolicy(args, opts) {
args = args || {};
opts = pulumi.mergeOptions(utilities.resourceOptsDefaults(), opts || {});
return pulumi.runtime.invoke("databricks:index/getAwsCrossAccountPolicy:getAwsCrossAccountPolicy", {
"awsAccountId": args.awsAccountId,
"awsPartition": args.awsPartition,
"passRoles": args.passRoles,
"policyType": args.policyType,
"region": args.region,
"securityGroupId": args.securityGroupId,
"vpcId": args.vpcId,
}, opts);
}
exports.getAwsCrossAccountPolicy = getAwsCrossAccountPolicy;
/**
* > **Note** This data source can only be used with an account-level provider!
*
* This data source constructs necessary AWS cross-account policy for you, which is based on [official documentation](https://docs.databricks.com/administration-guide/account-api/iam-role.html#language-Your%C2%A0VPC,%C2%A0default).
*
* ## Example Usage
*
* For more detailed usage please see databricks.getAwsAssumeRolePolicy or databricksAwsS3Mount pages.
*
* ```typescript
* import * as pulumi from "@pulumi/pulumi";
* import * as databricks from "@pulumi/databricks";
*
* const _this = databricks.getAwsCrossAccountPolicy({});
* ```
*
* ## Related Resources
*
* The following resources are used in the same context:
*
* * Provisioning AWS Databricks workspaces with a Hub & Spoke firewall for data exfiltration protection guide
* * databricks.getAwsAssumeRolePolicy data to construct the necessary AWS STS assume role policy.
* * databricks.getAwsBucketPolicy data to configure a simple access policy for AWS S3 buckets, so that Databricks can access data in it.
* * databricks.InstanceProfile to manage AWS EC2 instance profiles that users can launch databricks.Cluster and access data, like databricks_mount.
*/
function getAwsCrossAccountPolicyOutput(args, opts) {
args = args || {};
opts = pulumi.mergeOptions(utilities.resourceOptsDefaults(), opts || {});
return pulumi.runtime.invokeOutput("databricks:index/getAwsCrossAccountPolicy:getAwsCrossAccountPolicy", {
"awsAccountId": args.awsAccountId,
"awsPartition": args.awsPartition,
"passRoles": args.passRoles,
"policyType": args.policyType,
"region": args.region,
"securityGroupId": args.securityGroupId,
"vpcId": args.vpcId,
}, opts);
}
exports.getAwsCrossAccountPolicyOutput = getAwsCrossAccountPolicyOutput;
//# sourceMappingURL=getAwsCrossAccountPolicy.js.map