feat: global secret

[CrabHo]

• List

drone globalsecret ls

• Add

drone globalsecret add --name foo --value bar

• Info

drone globalsecret info --name foo

• Update

drone globalsecret update --name foo --event pull_request

• Remove

drone globalsecret rm --name foo

[laszlocph]

High quality PR.

Need a couple of days to crosscheck it with https://woodpecker.laszlo.cloud/environment-variables/#global-environment-variables
How the two features can co-exist.

What do you think about the feature overlap of the two?

[CrabHo]

env is for organization to setup non credentials data. e.g organization root domain, jira link or other data.

secret is for admin to set token like docker username and password.

in my opinion there are different purpose.

[laszlocph]

Thank you for the contributions. I'm now processing the backlog of PRs and my goal is to merge this in the coming days.

[laszlocph]

@CrabHo I see that this is building on top of the original Drone global secrets feature.

The problem here is that parts of that was not licensed with Apache2. I see that you pulled in the Apache code, but haven't got to the end in figuring out if all files are Apache or not.

It would help if you write down the approach you followed with the non Apache 2 code.

[Tchoupinax]

Hello folks,

What's up with this feature? :)

Moreover, are global secret shared with all repositories or only scoped with an organization?

[qwerty287]

I think this is now implemented in #1027 (which supports both global and organization levels), so we can close this?

[lafriks]

@qwerty287 I think yes, my PR fully replaces this one, except for drone cli part.

[lafriks]

I can implement CLI later on in other PR as I did not want to make PR too big :)