Support multiple environments for DEV/TEST/LIVE (other?)

Created on 27 February 2025, 8 days ago

Problem/Motivation

When configuring SAMLAUTH, your metadata generated, of course, matches the environment you're on.

This creates a chicken&egg scenario for "live" sites, which will have a different domain then your "DEV" or even "TEST" environments if you have that many.

How can one, support this module in CONFIG SYNC, when dealing with multiple environments?

example, using pantheon, at its simplest, you have 3 environments available to you.

dev-projectname.pantheonsite.io
test-projectname.pantheonsite.io
live-projectname.pantheonsite.io // yourrealdomain.com

Is it possible to support something like this in the module?

πŸ’¬ Support request
Status

Active

Version

4.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States alphex Atlanta, GA USA

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @alphex
  • πŸ‡³πŸ‡±Netherlands roderik Amsterdam,NL / Budapest,HU

    I rely on other people to specify their 'config sync' policy / best practices. So I'll rebrand this a task.

    People must be doing this. But so far, I don't remember anyone really commenting on it.

    Are they using config_ignore? If so, what are they ignoring? Just the entity ID (provided the certs are in files)?

    Do they want to use multiple IdP configs for this? ✨ Multiple IDP Support Needs work

    When there's a somewhat authoritative reply from someone, we can determine if this needs documentation, or other work.

Production build 0.71.5 2024