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

feat(api): disable project secrets auto injection for given regions #6048

Merged
merged 4 commits into from
Jan 4, 2022

Conversation

richardlt
Copy link
Member

  1. Description
  2. Related issues
  3. About tests
  4. Mentions

@ovh/cds

Copy link
Member

@fsamin fsamin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My suggestion would be to also add a piece of documentation about this advanced feature

engine/api/workflow_queue.go Outdated Show resolved Hide resolved
engine/api/workflow_queue.go Show resolved Hide resolved
sdk/requirement.go Show resolved Hide resolved
@richardlt richardlt force-pushed the feat-project-secrets-filter-region branch from 5a42189 to 6094e20 Compare December 29, 2021 15:55
@ovh ovh deleted a comment from ovh-cds Dec 29, 2021
@ovh ovh deleted a comment from ovh-cds Dec 29, 2021
@richardlt richardlt force-pushed the feat-project-secrets-filter-region branch from acc910a to a35a15c Compare December 29, 2021 18:18
@ovh ovh deleted a comment from ovh-cds Dec 29, 2021
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@richardlt richardlt merged commit 1ac7500 into master Jan 4, 2022
@richardlt richardlt deleted the feat-project-secrets-filter-region branch January 4, 2022 08:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants