Skip to content

config-manager: a kind for RemoteConsentAgent (later; not started) #1345

Open

Description

@vscheuber

Summary

Part of the tracking issue #1254. Maintainer decision (2026-11-16): RemoteConsentAgent stays on the generic kind now (G) and gets a kind of its own later (K). NOT STARTED: this issue only holds the disposition.

Generic by name today and in the help; dynamic per Ping's promotion FAQ ("Remote Consent"). Open fact to check before building: whether its schema holds a secret property (no secret override appears in the help or in the e2e input). If it does, the password convention of #1254 X7 applies (${<ID>_PASSWORD}-style placeholder derived from the object, a missing variable fails the push naming it, a pull without an override warns).

What to do when it is ordered

The recipe of the issuer kind (pull, push, delete, the pull all step, a skip entry in the shared table skippedForDedicatedKind), files where the generic kind wrote them, wrapped shape.

Depends on: #1259 and #1249 merged. Related: #1254.

Activity

  1. added
    enhancementNew feature or request
    no-auto-processingConcierge never touches this item; remove the label to hand it over
    on Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestno-auto-processingConcierge never touches this item; remove the label to hand it over

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions