Skip to content

bicepConfigs / terraformConfigs reject Radius.Security/secrets for registry secrets; only Applications.Core/secretStores accepted #12122

Description

@DariuszPorowski

Steps to reproduce

  1. Create a Radius.Security/secrets resource containing registry credentials.
  2. Create a Radius.Core/bicepConfig (or Radius.Core/terraformConfig) that references that secret for registryAuthentications/basicAuth.
  3. Apply the configuration (or run the functional test that references the config).
  4. Observe that the config is rejected or the secret reference is not accepted.

Example/test data that currently works (uses Applications.Core/secretStores):

Observed behavior

Radius.Core/bicepConfigs and Radius.Core/terraformConfigs accept Applications.Core/secretStores for registryAuthentications/basicAuth secret references, but attempts to reference Radius.Security/secrets are rejected or ignored. Functional test data in the repository uses Applications.Core/secretStores (see link above) and succeeds.

Desired behavior

Allow Radius.Security/secrets to be referenced by Radius.Core/bicepConfigs and Radius.Core/terraformConfigs as an equivalent secret resource. Additionally, Radius.Core/bicepConfigs and Radius.Core/terraformConfigs should be compatible with all the new extensibility architecture resources, including Radius.Core/applications, Radius.Core/environments, Radius.Security/secrets, etc.

Workaround

Workaround: Use Applications.Core/secretStores for registry secrets (this is what the current functional tests use).

rad Version

0.58.0

Operating system

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething is broken or not working as expectedcompute-extensibilitytriagedThis issue has been reviewed and triaged

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions