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: introduce v1beta1 version #526

Closed
wants to merge 6 commits into from

Conversation

odubajDT
Copy link
Contributor

@odubajDT odubajDT commented Oct 18, 2023

This PR

  • adds v1beta1 API

Related Issues

Part-of #352
Part-of #433

Follow-up

Notes

There is a problem with lint CI check, which is present on the main branch. This will be handled in a separate PR

Signed-off-by: odubajDT <ondrej.dubaj@dynatrace.com>
Signed-off-by: odubajDT <ondrej.dubaj@dynatrace.com>
@odubajDT odubajDT changed the title feat: instroduce v1beta1 version feat: introduce v1beta1 version Oct 18, 2023
@codecov
Copy link

codecov bot commented Oct 18, 2023

Codecov Report

Merging #526 (fd0daa5) into main (32ddf00) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #526   +/-   ##
=======================================
  Coverage   82.78%   82.78%           
=======================================
  Files          22       22           
  Lines        1423     1423           
=======================================
  Hits         1178     1178           
  Misses        207      207           
  Partials       38       38           
Flag Coverage Δ
unit-tests 82.78% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

@odubajDT odubajDT marked this pull request as ready for review October 18, 2023 08:59
@odubajDT odubajDT requested a review from a team as a code owner October 18, 2023 08:59
@odubajDT
Copy link
Contributor Author

There is a problem with lint CI check, which is present on the main branch. This will be handled in a separate PR

Signed-off-by: odubajDT <ondrej.dubaj@dynatrace.com>
Signed-off-by: odubajDT <ondrej.dubaj@dynatrace.com>
Signed-off-by: odubajDT <ondrej.dubaj@dynatrace.com>
Comment on lines +54 to +58
Image string `json:"image"`

// Tag to be appended to the sidecar image, defaults to 'main'
// +optional
Tag string `json:"tag"`
Copy link
Contributor

Choose a reason for hiding this comment

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

This is related to issue #517

This can be considered as a security concern and hence we can discuss on removing these

cc - @toddbaert @thisthat appreciate your opinion

Copy link
Contributor Author

Choose a reason for hiding this comment

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

adapted the code to remove tag and image from FlagSourceConfiguration CRD

Copy link
Member

@toddbaert toddbaert Oct 19, 2023

Choose a reason for hiding this comment

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

Ya I'm fine with removing them. I have only heard agreements on this.

I think we should come up with a short list of changes that we can include in the extended commit message.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

With further implementation I came across some issues regarding this. Read comment here #517 (comment)

I would suggest that covering this should be part of a separate PR, as it will bump the complexity of the PR, which will be adapting the code to use v1beta1 instead of v1alpha1. Any objections on this ?

Copy link
Member

@toddbaert toddbaert Oct 24, 2023

Choose a reason for hiding this comment

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

I agree we can adapt to use v1beta1 in a new PR, once we have that. OFO is locked to a particular version of flagd, so we shouldn't have breakage there.

It will be a breaking change in flagd though, so we should note that (with a feat!) so things are versioned accordingly. cc @thisthat @RealAnna


const (
SyncProviderKubernetes SyncProviderType = "kubernetes"
SyncProviderFilepath SyncProviderType = "filepath"
Copy link
Contributor

Choose a reason for hiding this comment

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

Please consider the diff highlighted in this related issue - #433

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Do we already have a unified solution? I see that the ticket does not clearly state which option to use

Copy link
Member

Choose a reason for hiding this comment

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

@beeme1mr @Kavindu-Dodan @thisthat which is better here? Any opinions? I suppose since we're already doing breaking changes here, it makes sense to concentrate them all here... so perhaps we should conform here in OFO to the flagd style: file.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

adapted to file

Copy link
Member

Choose a reason for hiding this comment

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

Signed-off-by: odubajDT <ondrej.dubaj@dynatrace.com>
@odubajDT
Copy link
Contributor Author

Closing in favor of #535

@odubajDT odubajDT closed this Oct 25, 2023
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.

3 participants