fix: override secrets from path

[csatib02]

Overview

• Fixes an issue, with seeing multiple secrets with the same key.

Fixes #202

Notes for reviewers

Functionality is manually tested with the following script:

# Set the Vault address
export VAULT_ADDR="http://127.0.0.1:8200"

# Set the Vault token
export VAULT_TOKEN=227e1cce-6bf7-30bb-2d2a-acc854318caf

# Set secret env-var
export MYSQL_PASSWORD=vault:secret/data/test/mysql#MYSQL_PASSWORD
export AWS_SECRET_ACCESS_KEY=vault:secret/data/test/aws#AWS_SECRET_ACCESS_KEY
export AWS_ACCESS_KEY_ID=vault:secret/data/test/aws#AWS_ACCESS_KEY_ID

export VAULT_FROM_PATH=secret/data/test/aws

# Run secret-init
go build
./secret-init env | grep 'MYSQL_PASSWORD\|AWS_SECRET_ACCESS_KEY\|AWS_ACCESS_KEY_ID'
rm secret-init

[ramizpolic]

we can register provider factories here and create them elsewhere

Suggested change

	var ProviderTypes = []provider.Provider{
	&file.Provider{},
	&vault.Provider{},
	&bao.Provider{},
	&aws.Provider{},
	&gcp.Provider{},
	&azure.Provider{},
	}
	var factories = []provider.ProviderFactory{
	file.NewProvider,
	vault.NewProvider,
	// and the rest
	}

since all provider operations are handled through env store, we can create providers there on demand in store constructor, for example

type EnvStore struct {
	data      map[string]string
	providers []provider.Provider
}

func NewEnvStore(ctx context.Context, config *common.Config) *EnvStore {
	// load env data
	environ := make(map[string]string, len(os.Environ()))
	for _, env := range os.Environ() {
		split := strings.SplitN(env, "=", 2)
		name := split[0]
		value := split[1]
		environ[name] = value
	}

	// create providers
	var providers []provider.Provider
	for _, factory := range factories {
		p, err := factory(ctx, config)
		if err != nil {
			return nil, fmt.Errorf("failed to create provider from factory: %w", err)
		}

		providers = append(providers, p)
	}

	return &EnvStore{
		data:      environ,
		providers: providers,
	}
}

You can now simply use provider slice to streamline all operations (including parallelization ops)

[ramizpolic]

if you need to use the specific provider type, id suggest to keep using the exposed consts (in this case, vault.ProviderName, or vault.ProviderType for usage clarity