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

Feature/1 merge blueprint versions #2

Open
wants to merge 21 commits into
base: develop
Choose a base branch
from

Conversation

ppxl
Copy link
Member

@ppxl ppxl commented Jan 21, 2025

This PR resolves #1 and moves blueprint related structs and high-level functionality from the cloudogu/k8s-blueprint-operator#103 here so other blueprint consuming clients can do so with a certain level of abstraction from the operator.

This code originated in cloudogu/blueprint-lib#1 but moves here because further development and refactoring can happen without two rather different code bases (from cesapp and the blueprint operator) to interfere. A two-repo way was specifically chosen over a mono-repo with two Go modules in it. This all to avoid different release strategies and manual mistakes in PR target branch selection (v1 -> a v1 branch/tag while develop -> v2).

ppxl added 21 commits January 16, 2025 08:54
This commit also fixes some minor typos, adds doc comments
and moves some higher-level definitions into bpcore since
v2 will probably make use of those as well.
This import was meant to compile as-is but some changes were necessary
to make it compile without domain or kubernetes package references. Long
story short, I needed to change a lot of things
This was changed during the extraction and was most likely a mistake.
The original code used string here.
This was changed during the extraction and was most likely a mistake.
The original code used string here.
This was changed during the extraction and was most likely a mistake.
The original code used string here.
Somehow these functions seem to be necessary by the blueprint operator's
deep copy generator even though I do not see where I might have deleted
it
These functions modified the input instead of the output. This commit
changes this so that the output is actually copied.
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.

Move blueprint-operator structs here
1 participant