propelauth.FeIntegration
Explore with Pulumi AI
Front-end Integration. This is for configuring the front-end integration for one of your project’s environments.
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as propelauth from "@pulumi/propelauth";
// Configure how the front-end of your application integrates with PropelAuth.
const example = new propelauth.FeIntegration("example", {
additionalFeLocations: [{
allowAnySubdomain: false,
domain: "http://localhost:3002",
}],
applicationUrl: "http://localhost:3001",
environment: "Test",
loginRedirectPath: "/home",
logoutRedirectPath: "/goodbye",
});
import pulumi
import pulumi_propelauth as propelauth
# Configure how the front-end of your application integrates with PropelAuth.
example = propelauth.FeIntegration("example",
additional_fe_locations=[{
"allow_any_subdomain": False,
"domain": "http://localhost:3002",
}],
application_url="http://localhost:3001",
environment="Test",
login_redirect_path="/home",
logout_redirect_path="/goodbye")
package main
import (
"github.com/pulumi/pulumi-terraform-provider/sdks/go/propelauth/propelauth"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
// Configure how the front-end of your application integrates with PropelAuth.
_, err := propelauth.NewFeIntegration(ctx, "example", &propelauth.FeIntegrationArgs{
AdditionalFeLocations: propelauth.FeIntegrationAdditionalFeLocationArray{
&propelauth.FeIntegrationAdditionalFeLocationArgs{
AllowAnySubdomain: pulumi.Bool(false),
Domain: pulumi.String("http://localhost:3002"),
},
},
ApplicationUrl: pulumi.String("http://localhost:3001"),
Environment: pulumi.String("Test"),
LoginRedirectPath: pulumi.String("/home"),
LogoutRedirectPath: pulumi.String("/goodbye"),
})
if err != nil {
return err
}
return nil
})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Propelauth = Pulumi.Propelauth;
return await Deployment.RunAsync(() =>
{
// Configure how the front-end of your application integrates with PropelAuth.
var example = new Propelauth.FeIntegration("example", new()
{
AdditionalFeLocations = new[]
{
new Propelauth.Inputs.FeIntegrationAdditionalFeLocationArgs
{
AllowAnySubdomain = false,
Domain = "http://localhost:3002",
},
},
ApplicationUrl = "http://localhost:3001",
Environment = "Test",
LoginRedirectPath = "/home",
LogoutRedirectPath = "/goodbye",
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.propelauth.FeIntegration;
import com.pulumi.propelauth.FeIntegrationArgs;
import com.pulumi.propelauth.inputs.FeIntegrationAdditionalFeLocationArgs;
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) {
// Configure how the front-end of your application integrates with PropelAuth.
var example = new FeIntegration("example", FeIntegrationArgs.builder()
.additionalFeLocations(FeIntegrationAdditionalFeLocationArgs.builder()
.allowAnySubdomain(false)
.domain("http://localhost:3002")
.build())
.applicationUrl("http://localhost:3001")
.environment("Test")
.loginRedirectPath("/home")
.logoutRedirectPath("/goodbye")
.build());
}
}
resources:
# Configure how the front-end of your application integrates with PropelAuth.
example:
type: propelauth:FeIntegration
properties:
additionalFeLocations:
- allowAnySubdomain: false
domain: http://localhost:3002
applicationUrl: http://localhost:3001
environment: Test
loginRedirectPath: /home
logoutRedirectPath: /goodbye
Create FeIntegration Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new FeIntegration(name: string, args: FeIntegrationArgs, opts?: CustomResourceOptions);
@overload
def FeIntegration(resource_name: str,
args: FeIntegrationArgs,
opts: Optional[ResourceOptions] = None)
@overload
def FeIntegration(resource_name: str,
opts: Optional[ResourceOptions] = None,
application_url: Optional[str] = None,
environment: Optional[str] = None,
login_redirect_path: Optional[str] = None,
logout_redirect_path: Optional[str] = None,
additional_fe_locations: Optional[Sequence[FeIntegrationAdditionalFeLocationArgs]] = None)
func NewFeIntegration(ctx *Context, name string, args FeIntegrationArgs, opts ...ResourceOption) (*FeIntegration, error)
public FeIntegration(string name, FeIntegrationArgs args, CustomResourceOptions? opts = null)
public FeIntegration(String name, FeIntegrationArgs args)
public FeIntegration(String name, FeIntegrationArgs args, CustomResourceOptions options)
type: propelauth:FeIntegration
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args FeIntegrationArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args FeIntegrationArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args FeIntegrationArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args FeIntegrationArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args FeIntegrationArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Constructor example
The following reference example uses placeholder values for all input properties.
var feIntegrationResource = new Propelauth.FeIntegration("feIntegrationResource", new()
{
ApplicationUrl = "string",
Environment = "string",
LoginRedirectPath = "string",
LogoutRedirectPath = "string",
AdditionalFeLocations = new[]
{
new Propelauth.Inputs.FeIntegrationAdditionalFeLocationArgs
{
Domain = "string",
AllowAnySubdomain = false,
},
},
});
example, err := propelauth.NewFeIntegration(ctx, "feIntegrationResource", &propelauth.FeIntegrationArgs{
ApplicationUrl: pulumi.String("string"),
Environment: pulumi.String("string"),
LoginRedirectPath: pulumi.String("string"),
LogoutRedirectPath: pulumi.String("string"),
AdditionalFeLocations: .FeIntegrationAdditionalFeLocationArray{
&.FeIntegrationAdditionalFeLocationArgs{
Domain: pulumi.String("string"),
AllowAnySubdomain: pulumi.Bool(false),
},
},
})
var feIntegrationResource = new FeIntegration("feIntegrationResource", FeIntegrationArgs.builder()
.applicationUrl("string")
.environment("string")
.loginRedirectPath("string")
.logoutRedirectPath("string")
.additionalFeLocations(FeIntegrationAdditionalFeLocationArgs.builder()
.domain("string")
.allowAnySubdomain(false)
.build())
.build());
fe_integration_resource = propelauth.FeIntegration("feIntegrationResource",
application_url="string",
environment="string",
login_redirect_path="string",
logout_redirect_path="string",
additional_fe_locations=[{
"domain": "string",
"allow_any_subdomain": False,
}])
const feIntegrationResource = new propelauth.FeIntegration("feIntegrationResource", {
applicationUrl: "string",
environment: "string",
loginRedirectPath: "string",
logoutRedirectPath: "string",
additionalFeLocations: [{
domain: "string",
allowAnySubdomain: false,
}],
});
type: propelauth:FeIntegration
properties:
additionalFeLocations:
- allowAnySubdomain: false
domain: string
applicationUrl: string
environment: string
loginRedirectPath: string
logoutRedirectPath: string
FeIntegration Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The FeIntegration resource accepts the following input properties:
- Application
Url string - The URL of the application that will be integrated with PropelAuth. This url is used in combination with the
login_redirect_path
andlogout_redirect_path
to redirect users to your application after logging in or out.application_url
must be a valid URL and can only be set forTest
environments. ForStaging
andProd
environments, theapplication_url
must be the verified domain for the environment or a subdomain of it. Seepropelauth.CustomDomainVerification
resource for more information. Do not include any trailing path separator (/
) in your URL. For example,https://any.subdomain.example.com
whereexample.com
has been verified. - Environment string
- The environment for which you are configuring the front-end integration. Accepted values are
Test
,Staging
, andProd
. - Login
Redirect stringPath - The URL path to redirect users to after they log in. This path is appended to the
application_url
to form the full URL. For example, ifapplication_url
ishttps://example.com
andlogin_redirect_path
is/dashboard
, the full URL will behttps://example.com/dashboard
. - Logout
Redirect stringPath - The URL path to redirect users to after they log out. This path is appended to the
application_url
to form the full URL. For example, ifapplication_url
ishttps://example.com
andlogout_redirect_path
is/goodbye
, the full URL will behttps://example.com/goodbye
. - Additional
Fe List<FeLocations Integration Additional Fe Location> - Additional front-end locations that are allowed to integrate with PropelAuth.
- Application
Url string - The URL of the application that will be integrated with PropelAuth. This url is used in combination with the
login_redirect_path
andlogout_redirect_path
to redirect users to your application after logging in or out.application_url
must be a valid URL and can only be set forTest
environments. ForStaging
andProd
environments, theapplication_url
must be the verified domain for the environment or a subdomain of it. Seepropelauth.CustomDomainVerification
resource for more information. Do not include any trailing path separator (/
) in your URL. For example,https://any.subdomain.example.com
whereexample.com
has been verified. - Environment string
- The environment for which you are configuring the front-end integration. Accepted values are
Test
,Staging
, andProd
. - Login
Redirect stringPath - The URL path to redirect users to after they log in. This path is appended to the
application_url
to form the full URL. For example, ifapplication_url
ishttps://example.com
andlogin_redirect_path
is/dashboard
, the full URL will behttps://example.com/dashboard
. - Logout
Redirect stringPath - The URL path to redirect users to after they log out. This path is appended to the
application_url
to form the full URL. For example, ifapplication_url
ishttps://example.com
andlogout_redirect_path
is/goodbye
, the full URL will behttps://example.com/goodbye
. - Additional
Fe []FeLocations Integration Additional Fe Location Args - Additional front-end locations that are allowed to integrate with PropelAuth.
- application
Url String - The URL of the application that will be integrated with PropelAuth. This url is used in combination with the
login_redirect_path
andlogout_redirect_path
to redirect users to your application after logging in or out.application_url
must be a valid URL and can only be set forTest
environments. ForStaging
andProd
environments, theapplication_url
must be the verified domain for the environment or a subdomain of it. Seepropelauth.CustomDomainVerification
resource for more information. Do not include any trailing path separator (/
) in your URL. For example,https://any.subdomain.example.com
whereexample.com
has been verified. - environment String
- The environment for which you are configuring the front-end integration. Accepted values are
Test
,Staging
, andProd
. - login
Redirect StringPath - The URL path to redirect users to after they log in. This path is appended to the
application_url
to form the full URL. For example, ifapplication_url
ishttps://example.com
andlogin_redirect_path
is/dashboard
, the full URL will behttps://example.com/dashboard
. - logout
Redirect StringPath - The URL path to redirect users to after they log out. This path is appended to the
application_url
to form the full URL. For example, ifapplication_url
ishttps://example.com
andlogout_redirect_path
is/goodbye
, the full URL will behttps://example.com/goodbye
. - additional
Fe List<FeLocations Integration Additional Fe Location> - Additional front-end locations that are allowed to integrate with PropelAuth.
- application
Url string - The URL of the application that will be integrated with PropelAuth. This url is used in combination with the
login_redirect_path
andlogout_redirect_path
to redirect users to your application after logging in or out.application_url
must be a valid URL and can only be set forTest
environments. ForStaging
andProd
environments, theapplication_url
must be the verified domain for the environment or a subdomain of it. Seepropelauth.CustomDomainVerification
resource for more information. Do not include any trailing path separator (/
) in your URL. For example,https://any.subdomain.example.com
whereexample.com
has been verified. - environment string
- The environment for which you are configuring the front-end integration. Accepted values are
Test
,Staging
, andProd
. - login
Redirect stringPath - The URL path to redirect users to after they log in. This path is appended to the
application_url
to form the full URL. For example, ifapplication_url
ishttps://example.com
andlogin_redirect_path
is/dashboard
, the full URL will behttps://example.com/dashboard
. - logout
Redirect stringPath - The URL path to redirect users to after they log out. This path is appended to the
application_url
to form the full URL. For example, ifapplication_url
ishttps://example.com
andlogout_redirect_path
is/goodbye
, the full URL will behttps://example.com/goodbye
. - additional
Fe FeLocations Integration Additional Fe Location[] - Additional front-end locations that are allowed to integrate with PropelAuth.
- application_
url str - The URL of the application that will be integrated with PropelAuth. This url is used in combination with the
login_redirect_path
andlogout_redirect_path
to redirect users to your application after logging in or out.application_url
must be a valid URL and can only be set forTest
environments. ForStaging
andProd
environments, theapplication_url
must be the verified domain for the environment or a subdomain of it. Seepropelauth.CustomDomainVerification
resource for more information. Do not include any trailing path separator (/
) in your URL. For example,https://any.subdomain.example.com
whereexample.com
has been verified. - environment str
- The environment for which you are configuring the front-end integration. Accepted values are
Test
,Staging
, andProd
. - login_
redirect_ strpath - The URL path to redirect users to after they log in. This path is appended to the
application_url
to form the full URL. For example, ifapplication_url
ishttps://example.com
andlogin_redirect_path
is/dashboard
, the full URL will behttps://example.com/dashboard
. - logout_
redirect_ strpath - The URL path to redirect users to after they log out. This path is appended to the
application_url
to form the full URL. For example, ifapplication_url
ishttps://example.com
andlogout_redirect_path
is/goodbye
, the full URL will behttps://example.com/goodbye
. - additional_
fe_ Sequence[Felocations Integration Additional Fe Location Args] - Additional front-end locations that are allowed to integrate with PropelAuth.
- application
Url String - The URL of the application that will be integrated with PropelAuth. This url is used in combination with the
login_redirect_path
andlogout_redirect_path
to redirect users to your application after logging in or out.application_url
must be a valid URL and can only be set forTest
environments. ForStaging
andProd
environments, theapplication_url
must be the verified domain for the environment or a subdomain of it. Seepropelauth.CustomDomainVerification
resource for more information. Do not include any trailing path separator (/
) in your URL. For example,https://any.subdomain.example.com
whereexample.com
has been verified. - environment String
- The environment for which you are configuring the front-end integration. Accepted values are
Test
,Staging
, andProd
. - login
Redirect StringPath - The URL path to redirect users to after they log in. This path is appended to the
application_url
to form the full URL. For example, ifapplication_url
ishttps://example.com
andlogin_redirect_path
is/dashboard
, the full URL will behttps://example.com/dashboard
. - logout
Redirect StringPath - The URL path to redirect users to after they log out. This path is appended to the
application_url
to form the full URL. For example, ifapplication_url
ishttps://example.com
andlogout_redirect_path
is/goodbye
, the full URL will behttps://example.com/goodbye
. - additional
Fe List<Property Map>Locations - Additional front-end locations that are allowed to integrate with PropelAuth.
Outputs
All input properties are implicitly available as output properties. Additionally, the FeIntegration resource produces the following output properties:
- Id string
- The provider-assigned unique ID for this managed resource.
- Id string
- The provider-assigned unique ID for this managed resource.
- id String
- The provider-assigned unique ID for this managed resource.
- id string
- The provider-assigned unique ID for this managed resource.
- id str
- The provider-assigned unique ID for this managed resource.
- id String
- The provider-assigned unique ID for this managed resource.
Look up Existing FeIntegration Resource
Get an existing FeIntegration resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: FeIntegrationState, opts?: CustomResourceOptions): FeIntegration
@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
additional_fe_locations: Optional[Sequence[FeIntegrationAdditionalFeLocationArgs]] = None,
application_url: Optional[str] = None,
environment: Optional[str] = None,
login_redirect_path: Optional[str] = None,
logout_redirect_path: Optional[str] = None) -> FeIntegration
func GetFeIntegration(ctx *Context, name string, id IDInput, state *FeIntegrationState, opts ...ResourceOption) (*FeIntegration, error)
public static FeIntegration Get(string name, Input<string> id, FeIntegrationState? state, CustomResourceOptions? opts = null)
public static FeIntegration get(String name, Output<String> id, FeIntegrationState state, CustomResourceOptions options)
resources: _: type: propelauth:FeIntegration get: id: ${id}
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- Additional
Fe List<FeLocations Integration Additional Fe Location> - Additional front-end locations that are allowed to integrate with PropelAuth.
- Application
Url string - The URL of the application that will be integrated with PropelAuth. This url is used in combination with the
login_redirect_path
andlogout_redirect_path
to redirect users to your application after logging in or out.application_url
must be a valid URL and can only be set forTest
environments. ForStaging
andProd
environments, theapplication_url
must be the verified domain for the environment or a subdomain of it. Seepropelauth.CustomDomainVerification
resource for more information. Do not include any trailing path separator (/
) in your URL. For example,https://any.subdomain.example.com
whereexample.com
has been verified. - Environment string
- The environment for which you are configuring the front-end integration. Accepted values are
Test
,Staging
, andProd
. - Login
Redirect stringPath - The URL path to redirect users to after they log in. This path is appended to the
application_url
to form the full URL. For example, ifapplication_url
ishttps://example.com
andlogin_redirect_path
is/dashboard
, the full URL will behttps://example.com/dashboard
. - Logout
Redirect stringPath - The URL path to redirect users to after they log out. This path is appended to the
application_url
to form the full URL. For example, ifapplication_url
ishttps://example.com
andlogout_redirect_path
is/goodbye
, the full URL will behttps://example.com/goodbye
.
- Additional
Fe []FeLocations Integration Additional Fe Location Args - Additional front-end locations that are allowed to integrate with PropelAuth.
- Application
Url string - The URL of the application that will be integrated with PropelAuth. This url is used in combination with the
login_redirect_path
andlogout_redirect_path
to redirect users to your application after logging in or out.application_url
must be a valid URL and can only be set forTest
environments. ForStaging
andProd
environments, theapplication_url
must be the verified domain for the environment or a subdomain of it. Seepropelauth.CustomDomainVerification
resource for more information. Do not include any trailing path separator (/
) in your URL. For example,https://any.subdomain.example.com
whereexample.com
has been verified. - Environment string
- The environment for which you are configuring the front-end integration. Accepted values are
Test
,Staging
, andProd
. - Login
Redirect stringPath - The URL path to redirect users to after they log in. This path is appended to the
application_url
to form the full URL. For example, ifapplication_url
ishttps://example.com
andlogin_redirect_path
is/dashboard
, the full URL will behttps://example.com/dashboard
. - Logout
Redirect stringPath - The URL path to redirect users to after they log out. This path is appended to the
application_url
to form the full URL. For example, ifapplication_url
ishttps://example.com
andlogout_redirect_path
is/goodbye
, the full URL will behttps://example.com/goodbye
.
- additional
Fe List<FeLocations Integration Additional Fe Location> - Additional front-end locations that are allowed to integrate with PropelAuth.
- application
Url String - The URL of the application that will be integrated with PropelAuth. This url is used in combination with the
login_redirect_path
andlogout_redirect_path
to redirect users to your application after logging in or out.application_url
must be a valid URL and can only be set forTest
environments. ForStaging
andProd
environments, theapplication_url
must be the verified domain for the environment or a subdomain of it. Seepropelauth.CustomDomainVerification
resource for more information. Do not include any trailing path separator (/
) in your URL. For example,https://any.subdomain.example.com
whereexample.com
has been verified. - environment String
- The environment for which you are configuring the front-end integration. Accepted values are
Test
,Staging
, andProd
. - login
Redirect StringPath - The URL path to redirect users to after they log in. This path is appended to the
application_url
to form the full URL. For example, ifapplication_url
ishttps://example.com
andlogin_redirect_path
is/dashboard
, the full URL will behttps://example.com/dashboard
. - logout
Redirect StringPath - The URL path to redirect users to after they log out. This path is appended to the
application_url
to form the full URL. For example, ifapplication_url
ishttps://example.com
andlogout_redirect_path
is/goodbye
, the full URL will behttps://example.com/goodbye
.
- additional
Fe FeLocations Integration Additional Fe Location[] - Additional front-end locations that are allowed to integrate with PropelAuth.
- application
Url string - The URL of the application that will be integrated with PropelAuth. This url is used in combination with the
login_redirect_path
andlogout_redirect_path
to redirect users to your application after logging in or out.application_url
must be a valid URL and can only be set forTest
environments. ForStaging
andProd
environments, theapplication_url
must be the verified domain for the environment or a subdomain of it. Seepropelauth.CustomDomainVerification
resource for more information. Do not include any trailing path separator (/
) in your URL. For example,https://any.subdomain.example.com
whereexample.com
has been verified. - environment string
- The environment for which you are configuring the front-end integration. Accepted values are
Test
,Staging
, andProd
. - login
Redirect stringPath - The URL path to redirect users to after they log in. This path is appended to the
application_url
to form the full URL. For example, ifapplication_url
ishttps://example.com
andlogin_redirect_path
is/dashboard
, the full URL will behttps://example.com/dashboard
. - logout
Redirect stringPath - The URL path to redirect users to after they log out. This path is appended to the
application_url
to form the full URL. For example, ifapplication_url
ishttps://example.com
andlogout_redirect_path
is/goodbye
, the full URL will behttps://example.com/goodbye
.
- additional_
fe_ Sequence[Felocations Integration Additional Fe Location Args] - Additional front-end locations that are allowed to integrate with PropelAuth.
- application_
url str - The URL of the application that will be integrated with PropelAuth. This url is used in combination with the
login_redirect_path
andlogout_redirect_path
to redirect users to your application after logging in or out.application_url
must be a valid URL and can only be set forTest
environments. ForStaging
andProd
environments, theapplication_url
must be the verified domain for the environment or a subdomain of it. Seepropelauth.CustomDomainVerification
resource for more information. Do not include any trailing path separator (/
) in your URL. For example,https://any.subdomain.example.com
whereexample.com
has been verified. - environment str
- The environment for which you are configuring the front-end integration. Accepted values are
Test
,Staging
, andProd
. - login_
redirect_ strpath - The URL path to redirect users to after they log in. This path is appended to the
application_url
to form the full URL. For example, ifapplication_url
ishttps://example.com
andlogin_redirect_path
is/dashboard
, the full URL will behttps://example.com/dashboard
. - logout_
redirect_ strpath - The URL path to redirect users to after they log out. This path is appended to the
application_url
to form the full URL. For example, ifapplication_url
ishttps://example.com
andlogout_redirect_path
is/goodbye
, the full URL will behttps://example.com/goodbye
.
- additional
Fe List<Property Map>Locations - Additional front-end locations that are allowed to integrate with PropelAuth.
- application
Url String - The URL of the application that will be integrated with PropelAuth. This url is used in combination with the
login_redirect_path
andlogout_redirect_path
to redirect users to your application after logging in or out.application_url
must be a valid URL and can only be set forTest
environments. ForStaging
andProd
environments, theapplication_url
must be the verified domain for the environment or a subdomain of it. Seepropelauth.CustomDomainVerification
resource for more information. Do not include any trailing path separator (/
) in your URL. For example,https://any.subdomain.example.com
whereexample.com
has been verified. - environment String
- The environment for which you are configuring the front-end integration. Accepted values are
Test
,Staging
, andProd
. - login
Redirect StringPath - The URL path to redirect users to after they log in. This path is appended to the
application_url
to form the full URL. For example, ifapplication_url
ishttps://example.com
andlogin_redirect_path
is/dashboard
, the full URL will behttps://example.com/dashboard
. - logout
Redirect StringPath - The URL path to redirect users to after they log out. This path is appended to the
application_url
to form the full URL. For example, ifapplication_url
ishttps://example.com
andlogout_redirect_path
is/goodbye
, the full URL will behttps://example.com/goodbye
.
Supporting Types
FeIntegrationAdditionalFeLocation, FeIntegrationAdditionalFeLocationArgs
- Domain string
- A domain that will also be allowed to access user information. The domain must include a scheme. For example,
https://example.com
. - Allow
Any boolSubdomain - If true, any subdomain of the domain to integrate with PropelAuth is also allowed to access user info. The default value is false.
- Domain string
- A domain that will also be allowed to access user information. The domain must include a scheme. For example,
https://example.com
. - Allow
Any boolSubdomain - If true, any subdomain of the domain to integrate with PropelAuth is also allowed to access user info. The default value is false.
- domain String
- A domain that will also be allowed to access user information. The domain must include a scheme. For example,
https://example.com
. - allow
Any BooleanSubdomain - If true, any subdomain of the domain to integrate with PropelAuth is also allowed to access user info. The default value is false.
- domain string
- A domain that will also be allowed to access user information. The domain must include a scheme. For example,
https://example.com
. - allow
Any booleanSubdomain - If true, any subdomain of the domain to integrate with PropelAuth is also allowed to access user info. The default value is false.
- domain str
- A domain that will also be allowed to access user information. The domain must include a scheme. For example,
https://example.com
. - allow_
any_ boolsubdomain - If true, any subdomain of the domain to integrate with PropelAuth is also allowed to access user info. The default value is false.
- domain String
- A domain that will also be allowed to access user information. The domain must include a scheme. For example,
https://example.com
. - allow
Any BooleanSubdomain - If true, any subdomain of the domain to integrate with PropelAuth is also allowed to access user info. The default value is false.
Import
Import using the target environment as the ID: Test
, Staging
, or Prod
.
$ pulumi import propelauth:index/feIntegration:FeIntegration prod_example Prod
To learn more about importing existing cloud resources, see Importing resources.
Package Details
- Repository
- propelauth propelauth/terraform-provider-propelauth
- License
- Notes
- This Pulumi package is based on the
propelauth
Terraform Provider.