cyberark / summon-s3 Goto Github PK

View Code? Open in Web Editor NEW

13.0 22.0 6.0 6.99 MB

AWS S3 provider for Summon

License: MIT License

Shell 71.61% Go 28.39%

aws-s3 summon summon-provider conjbot-notify conjur-community-team

summon-s3's Introduction

summon-s3

AWS S3 provider for Summon.

Provides access to secrets stored in Amazon S3.

Usage

Set summon-s3 as your Summon provider.

Give summon a path to an object in S3 and it will fetch it for you and print the value to stdout.

summon --provider summon-s3 \
--yaml 'MONGOPASS: !var myorg-creds/aws/dev/mongodb-password' \
printenv MONGOPASS
8h9psadf89sdahfp98

myorg-credentials is the bucket name.

Configuration

summon-s3 uses the official AWS Go SDK (V2). It will use the credentials file or environment variables as they explain.

Contributing

We welcome contributions of all kinds to this repository. For instructions on how to get started and descriptions of our development workflows, please see our contributing guide.

summon-s3's People

Contributors

Stargazers

Watchers

Forkers

pcbng slimm609 scalp42 ekmixon

summon-s3's Issues

The binary doesn't work on alpine

The binary does not work on alpine linux:

# ./summon-s3
sh: ./summon-s3: not found

It seems it's because of glibc dependency. To fix it, the binary should either be statically compiled, or a separate binary for musl should be provided.

(Originally reported by @chrisdostert as cyberark/summon#20)

ECS task roles error

summon s3 won't pull from a container with ECS roles because the version of aws-sdk-go is to old to support it. A rebuild with updated deps should resolve the issue.

I tried to update all the deps but I am getting these errors below while building. I don't know go well enough to resolve this issue.

-->     linux/amd64: github.com/conjurinc/summon-s3
-->   windows/amd64: github.com/conjurinc/summon-s3

3 errors occurred:
--> darwin/amd64 error: exit status 2
Stderr: # github.com/aws/aws-sdk-go/aws/request
Godeps/_workspace/src/github.com/aws/aws-sdk-go/aws/request/request_context_1_6.go:13: r.HTTPRequest.Cancel undefined (type *http.Request has no field or method Cancel)

--> linux/amd64 error: exit status 2
Stderr: # github.com/aws/aws-sdk-go/aws/request
Godeps/_workspace/src/github.com/aws/aws-sdk-go/aws/request/request_context_1_6.go:13: r.HTTPRequest.Cancel undefined (type *http.Request has no field or method Cancel)

--> windows/amd64 error: exit status 2
Stderr: # github.com/aws/aws-sdk-go/aws/request
Godeps/_workspace/src/github.com/aws/aws-sdk-go/aws/request/request_context_1_6.go:13: r.HTTPRequest.Cancel undefined (type *http.Request has no field or method Cancel)

Installation instructions

It'd be great if installation instructions could be added/linked to in README.

standardised CHANGELOG exists, and is validated via pipeline

If the repo has a changelog that doesn't meet the standard, do try to change earlier entries to match the standard.
If the repo doesn't have a changelog use this as a starter:

# Changelog
All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).

## [Unreleased]

Acceptance criteria

CHANGELOG.md exists and follows the KeepAChangeLog format. For reference consult https://github.com/cyberark/conjur/blob/master/CHANGELOG.md.
Add parse-changelog validation step to Jenkinsfile. For reference consult https://github.com/cyberark/conjur/blob/master/Jenkinsfile#L27.

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

Apple silicon is not supported.

Describe the solution you would like

GoReleaser should build an Apple M1

Describe alternatives you have considered

A clear and concise description of any alternative solutions or features that may be related to this that
you have considered.

Additional context

Add any other context information about the feature request here.