Close #5338 Allow setting profiles api key and endpoint organization wide.

[trackleft]

Description

The service may be overkill, but I didn't want this integration to break sites with the following circumstance.

• Have an existing apikey and endpoint set for profiles api.
• Have az_secrets or pantheon_secrets modules already enabled
• No Organization wide apikey set for profiles importer.
• No Organization wide endpoint set for profiles importer.

Release notes

Related issues

#5338

How to test

Types of changes

Arizona Quickstart (install profile, custom modules, custom theme)

• Patch release changes
  • Bug fix
  • Accessibility, performance, or security improvement
  • Critical institutional link or brand change
  • Adding experimental module
  • Update experimental module
• Minor release changes
  • New feature
  • Breaking or visual change to existing behavior
  • Upgrade experimental module to stable
  • Enable existing module by default or database update
  • Non-critical brand change
  • New internal API or API improvement with backwards compatibility
  • Risky or disruptive cleanup to comply with coding standards
  • High-risk or disruptive change (requires upgrade path, risks regression, etc.)
• Other or unknown
  • Other or unknown

Drupal core

• Patch release changes
  • Security update
  • Patch level release (non-security bug-fix release)
  • Patch removal that's no longer necessary
• Minor release changes
  • Major or minor level update
• Other or unknown
  • Other or unknown

Drupal contrib projects

• Patch release changes
  • Security update
  • Patch or minor level update
  • Add new module
  • Patch removal that's no longer necessary
• Minor release changes
  • Major level update
• Other or unknown
  • Other or unknown

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My change requires release notes.

[joeparsons]

The service may be overkill, but I didn't want this integration to break sites with the following circumstance.

• Have an existing apikey and endpoint set for profiles api.
• Have az_secrets or pantheon_secrets modules already enabled
• No Organization wide apikey set for profiles importer.
• No Organization wide endpoint set for profiles importer.

I don't think the service is needed. Our existing AZSecrets KeyProvider plugin and the Key module itself should already prevent these circumstances from causing issues.

See:

• AZSecrets.php#L119-L121
• KeyConfigOverrides.php#L90-95