ouzi-dev / credstash-operator Goto Github PK

Currently, only Secrets of type Opaque will be created and managed.

It would be nice if we could also manage dockerconfig type secrets such that we can manage those as well via credstash

As a user, I would like to be able to create dockerconfig type secrets from a crestash secret that contains the docker config json.

As a user, i would like to see if the controller has successfully fetched the secrets from credstash when doing a kubectl get credstashsecrets

Dependabot couldn't parse the go.mod found at /go.mod.

The error Dependabot encountered was:

go: github.com/operator-framework/[email protected] requires
	github.com/operator-framework/[email protected] requires
	github.com/openshift/[email protected]+incompatible: invalid pseudo-version: preceding tag (v3.9.0) not found

View the update logs.

Describe the feature
It would be nice to use IAM Roles and Web Identities when deploying the controller (especially useful when on EKS) instead of hardcoding keys.

What would the new user story look like?
How would the new interaction with Credstash Operator look like? E.g.

1. What are the prerequisites for this? On an AWS environment
2. User starts up Credstash Operator using the --use-iam-role or --use-web-identity
3. User submits CredstashSecret object with extra parameter new-feature
4. New Secret created using the new feature

Hi! 👋🏻

Have you considered listing the credstash operator directly in Artifact Hub?

At the moment it is already listed there, because the Artifact Hub team has added the community-operators repository. However, listing it yourself directly has some benefits:

• You add your repository once, and new versions (or even new operators) committed to your git repository will be indexed automatically and listed in Artifact Hub, with no extra PRs needed.
• You can display the Verified Publisher label in your operators, increasing their visibility and potentially the users' trust in your content.
• Increased visibility of your organization in urls and search results. Users will be able to see your organization's description, a link to the home page and search for other content published by you.
• If something goes wrong indexing your repository, you will be notified and you can even inspect the logs to check what went wrong.

If you decide to go ahead, you just need to sign in and add your repository from the control panel. You can add it using a single user or create an organization for it, whatever suits your needs best.

You can find some notes about the expected repository url format and repository structure in the repositories guide. There is also available an example of an operator repository already listed in Artifact Hub in the documentation. Operators are expected to be packaged using the format defined in the Operator Framework documentation to facilitate the process.

Please let me know if you have any questions or if you encounter any issue during the process 🙂

Dependabot can't resolve your Go dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

verifying github.com/mikefarah/yaml/[email protected]/go.mod: checksum mismatch

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.

Dependabot can't resolve your Go dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

vbom.ml/[email protected]: unrecognized import path "vbom.ml/util" (https fetch: Get https://vbom.ml/util?go-get=1: EOF)

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.