Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add secret type credential to validation code #308

Merged
merged 4 commits into from
Sep 20, 2019

Conversation

hakanmemisoglu
Copy link
Contributor

@hakanmemisoglu hakanmemisoglu commented Sep 20, 2019

Change Overview

Add secret type credential to validation code.

Pull request type

Please check the type of change your PR introduces:

  • Work in Progress
  • Refactoring (no functional changes, no api changes)
  • Trivial/Minor
  • Bugfix
  • Feature
  • Documentation

Test Plan

  • Manual
  • Unit test
  • E2E

@SupriyaKasten
Copy link
Contributor

Looks good to me @hakanmemisoglu ! Do we have a failure case for crv1alpha1.CredentialTypeKeyPair in TestProfileSchema() ?

@hakanmemisoglu
Copy link
Contributor Author

@SupriyaKasten Let me add it.

@SupriyaKasten
Copy link
Contributor

@SupriyaKasten Let me add it.

Thanks 🚀

@mergify mergify bot merged commit 9178d4c into master Sep 20, 2019
hakanmemisoglu pushed a commit that referenced this pull request Sep 20, 2019
mergify bot pushed a commit that referenced this pull request Sep 20, 2019
* Revert "Update getOSSecret to use Secret credentials in AWS (#309)"

This reverts commit 2192605.

* Revert "Add secret type credential to validation code (#308)"

This reverts commit 9178d4c.

* Revert "Support creating S3 args from Secret type Credential (#305)"

This reverts commit d8f7d76.

* Revert "Add secret type for Param.Credentials (#300)"

This reverts commit ad3cbce.
@pavannd1 pavannd1 deleted the add-secret-type-to-validation branch October 1, 2019 21:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants