Adding possibility to include Authorization header when using externa…

[vmladenovic]

…l extension marketplace

Fixes #7595

[code-asher]

Nice I like this! I think there might be some types that also need to be updated, but CI should tell us more once it runs.

I wonder if we can be more descriptive than token. Maybe authorizationHeaderToken? Or...hmm should we make it a general headers property maybe?? Then users could add whatever headers they need.

[code-asher]

Could we revert all these path changes that rename code-server to coder-code-server-fork?

[vmladenovic]

Nice I like this! I think there might be some types that also need to be updated, but CI should tell us more once it runs.

I wonder if we can be more descriptive than token. Maybe authorizationHeaderToken? Or...hmm should we make it a general headers property maybe?? Then users could add whatever headers they need.

I guess we could be more descriptive and use authorizationHeaderToken. My idea was to keep it really simple so I wouldn't go with the general "header" property for now if it's OK with you?

[code-asher]

I have this suspicion that this is one of those things that ends up being replaced by a generic solution and then we are stuck maintaining the old thing forever hahaha but this is tiny enough that it should be no problem to deprecate in the future if necessary. We have no idea if we really need a generic solution anyway, maybe this will be the only header we need.

Thanks again!