anonymous_username is an unknown field

[jameswestnz]

When running kongfig apply, I am getting the following error in the terminal:

PATCH http://kong:8001/plugins/463f37be-6f14-4891-a725-2ae6d81e384a
  { enabled: true,
   config: { anonymous_username: 'unauthorized' } }
 400 Bad Request { 'config.anonymous_username': 'anonymous_username is an unknown field' }
 Error: Bad Request
 {"config.anonymous_username":"anonymous_username is an unknown field"}

Excerpt from config file (plugins is global, not under an api):

plugins: 
  - name: basic-auth
    attributes:
      enabled: true
      config:
        anonymous_username: unauthorized

It seems the anonymous_username property only works when a plugin is defined under an API. Is this intended? I was hoping to define an anonymous user at the global level - maybe I'm missing something?

[jameswestnz]

Looking at the source code that's being installed via npm or yarn, it looks like version 1.4.1 doesn't have this feature?

Here's the function locally:

function _globalPlugin(plugin) {
    validateEnsure(plugin.ensure);

    return function (world) {
        if (plugin.ensure == 'removed') {
            if (world.hasGlobalPlugin(plugin.name)) {
                return (0, _actions.removeGlobalPlugin)(world.getGlobalPluginId(plugin.name));
            }

            return (0, _actions.noop)({ type: 'noop-global-plugin', plugin: plugin });
        }

        if (world.hasGlobalPlugin(plugin.name)) {
            if (world.isGlobalPluginUpToDate(plugin)) {
                return (0, _actions.noop)({ type: 'noop-global-plugin', plugin: plugin });
            }

            return (0, _actions.updateGlobalPlugin)(world.getGlobalPluginId(plugin.name), plugin.attributes);
        }

        return (0, _actions.addGlobalPlugin)(plugin.name, plugin.attributes);
    };
}

EDIT: Here's npmjs' current 1.4.1 - https://registry.npmjs.org/kongfig/-/kongfig-1.4.1.tgz

[CyExy]

Looks like the 1.4.1 release had gone wrong and an earlier version was published, in github it is correct but in npm registry it is incorrect. Please try again with 1.4.2.

[CyExy]

This should be fixed, please re-open if still happening