Skip to content

feat: build tags for all the providers to disable them on demand #5295

@Skarlso

Description

@Skarlso

Is your feature request related to a problem? Please describe.

The idea is that all the providers get their own build tags. Say go:aws go:gcp go:vault etc.

In the register file in which we include all of them, we can also add their build tags.

This adds the ability that people who are very security focus can actually disable ALL the source code for a provider they don't want to use and actually only include the provider they DO want to use.

So a build could be created in which only the code is included that lets you deal with AWS provider. This further strengthens the security posture of ESO because other providers couldn't bleed into the only providers being used by the user.

Note: ESO would ALWAYS build ALL of the providers. This is strictly a user operated feature. If users would like to opt-out from providers they need to build their own ESO with the right build flags.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Metadata

Metadata

Assignees

Labels

good first issueGood for newcomerskind/featureCategorizes issue or PR as related to a new feature.track/providerscapture issues related to providers

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions