"configuration" field in configuration extension request

[sloonz]

I’m trying to migrate to Woodpecker 3.x, and I’m confused as hell.

I didn’t migrate because I use a configuration extension that transforms a configuration. Which means that it needs to be provided the initial configuration in the request sent by woodpecker to the extension. Which has been removed by 3.x, see the discussion here : #4017

In that discussion, it was said "And I think in #3349 this is added back to the per-repo option", so I decided to wait and see. Now #3349, and the documentation (https://woodpecker-ci.org/docs/usage/extensions/configuration-extension) states :

The extension receives an HTTP POST request with the following JSON payload:

class Request {
  repo: Repo;
  pipeline: Pipeline;
  netrc: Netrc;
  configuration: {
    name: string; // filename of the configuration file
    data: string; // content of the configuration file
  }[];
}

But where I try to point it to my configuration extension, I get :

{
  "repo": {
    ...  
  },
  "pipeline": {
    ...
  },
  "netrc": {
    "machine": "localhost",
    "login": "root",
    "password": "[redacted]",
    "type": "forgejo"
  }
}

So… is "configuration" supposed to be present in the request sent by woodpecker ?

[qwerty287]

Yes you're right, this is a bug. The data is not sent at all right now. You can try using the netrc data to fetch the config till this would get fixed. I can open a pr to fix it next week.

[sloonz]

Thanks. I’ve made the fix + PR, if it helps : #5831.