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

Conditional publishing for K8s swagger specs #3

Open
jjzazuet opened this issue Aug 21, 2024 · 0 comments
Open

Conditional publishing for K8s swagger specs #3

jjzazuet opened this issue Aug 21, 2024 · 0 comments

Comments

@jjzazuet
Copy link
Contributor

So, Maven Central won't allow artifact updates for the same version. For example:

  • Beleth upgrades to version 0.2.X.
  • All K8S definitions remain at their latest versions. For example:
    • k8s130:1.30.3
    • k8s130:1.31.0

So here, we should only publish bl-rt, and keep all other artifacts the same, since they already have been published.

Or

  • Beleth remains at version 0.2.X.
  • At least one K8S definition set upgrades versions. For example:
    • k8s130:1.30.4
    • k8s130:1.31.0

Here, we should just publish k8s130:1.30.4.

So therefore, the build process needs to be smart enough to know which artifacts will get updated when a new release gets published.

Alternatively, we could:

  1. Extract the code generation library to its own artifact.
  2. Have bl-codegen, bl-rt and friends follow the same release version.
  3. Maintain the K8S class definitions as separate projects.

Open to any other options.

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

No branches or pull requests

1 participant