-
Notifications
You must be signed in to change notification settings - Fork 108
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
Introducing v2alpha1 #374
Introducing v2alpha1 #374
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This pull request does not contain a valid label. Please add one of the following labels: bug, enhancement, documentation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM from documentation perspective
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💯
@@ -5,6 +5,7 @@ resources: | |||
- bases/v1beta1/datadoghq.com_datadogagents.yaml | |||
- bases/v1beta1/datadoghq.com_datadogmetrics.yaml | |||
- bases/v1beta1/datadoghq.com_datadogmonitors.yaml | |||
- bases/datadoghq.com_datadogagents.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should not be present
* restructuring project to support multi-group * adding storage option and new openapi gen * adding v2alpha1
What does this PR do?
containerSymlinksPath
andConfigDirSpec.Items
using the atomic list and here.Motivation
We are going to introduce a new API that will carry breaking changes, this PR is the foundation of the migration.
Additional Notes
Anything else we should know when reviewing?
Describe your test plan
Transparent change for now, only issue would be if someone vendors the project.