Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deploying SSO should not require metering and replicator inputs #47

Open
felixzieger opened this issue Aug 8, 2024 · 0 comments
Open

Comments

@felixzieger
Copy link
Contributor

If you only want to enable SSO by integrating Entra ID as an identity provider for meshStack, you can use this module, but are forced to configure some unrelated parts of replicator and metering.

The following is a minimal config you can apply

provider "azurerm" {
  features {}
}

module "meshplatform" {
      source = "git::https://github.com/meshcloud/terraform-azure-meshplatform.git"
      sso_enabled = true
      sso_meshstack_idp_domain = "[sso.<name>.meshstack.io](http://sso.<name>.meshstack.io/)"
      sso_identity_provider_alias = "oidc"
      replicator_enabled = false
      metering_enabled = false
      replicator_assignment_scopes = []
      replicator_custom_role_scope = "<id of management group>"
      metering_assignment_scopes = []

}
output "meshplatform" {
      sensitive = true
      value     = module.meshplatform
}

Expected minimal input

module "meshplatform" {
source = "git::https://github.com/meshcloud/terraform-azure-meshplatform.git"
sso_enabled = true
sso_meshstack_idp_domain = "sso..meshstack.io"
sso_identity_provider_alias = "oidc"
replicator_enabled = false
metering_enabled = false
}
output "meshplatform" {
sensitive = true
value = module.meshplatform
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant