Skip to content

ccg-plugin job from winc/2.24.0

Github source: bad62c3 or master branch

Properties

ccg

credential_spec

JSON string describing the GMSA user account and domain details. See https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/manage-serviceaccounts#create-a-credential-spec

Example
|+
  {
    "CmsPlugins": [
      "ActiveDirectory"
    ],
    "DomainJoinConfig": {
      "Sid": "S-1-5-21-702590844-1001920913-2680819671",
      "MachineAccountName": "webapp01",
      "Guid": "56d9b66c-d746-4f87-bd26-26760cfdca2e",
      "DnsTreeName": "contoso.com",
      "DnsName": "contoso.com",
      "NetBiosName": "CONTOSO"
    },
    "ActiveDirectoryConfig": {
      "GroupManagedServiceAccounts": [
        {
          "Name": "webapp01",
          "Scope": "contoso.com"
        },
        {
          "Name": "webapp01",
          "Scope": "CONTOSO"
        }
      ]
    }
  }

enabled

When enabled, winc will pass a credential spec to HCS on container creation.

Default
false

plugin_guid

The curly-brace-enclosed GUID of the COM class which implements the ICcgDomainAuthCredentials::GetPasswordCredentials method. See https://docs.microsoft.com/en-us/windows/win32/api/ccgplugins/nf-ccgplugins-iccgdomainauthcredentials-getpasswordcredentials.

Default
'{8019A64C-3F4E-4DE3-AD2B-9A544290E2C3}'

plugin_input

The input to the plugin used to resolve credentials from Active Directory. See https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/manage-serviceaccounts#additional-credential-spec-configuration-for-non-domain-joined-container-host-use-case

Templates

Templates are rendered and placed onto corresponding instances during the deployment process. This job's templates will be placed into /var/vcap/jobs/ccg-plugin/ directory (learn more).

  • bin/post-stop.ps1 (from post-stop.ps1.erb)
  • bin/pre-start.ps1 (from pre-start.ps1.erb)
  • config/credential_spec.json (from credential_spec.json.erb)

Packages

Packages are compiled and placed onto corresponding instances during the deployment process. Packages will be placed into /var/vcap/packages/ directory.