-
Notifications
You must be signed in to change notification settings - Fork 132
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
GA: Promote Receiver
to notification.toolkit.fluxcd.io/v1
#436
Milestone
Comments
makkes
added a commit
that referenced
this issue
Mar 20, 2023
refs #436 Signed-off-by: Max Jonas Werner <[email protected]>
makkes
pushed a commit
that referenced
this issue
Mar 22, 2023
This commit bumps the Receiver API version to v1 in preparation of the Flux GitOps GA milestone (https://fluxcd.io/roadmap/#flux-gitops-ga-q1-2023). We are now actively maintaining two versions of the notification API group in parallel: v1 which currently only holds the Receiver kind and v1beta2 for all other kinds. Since we haven't run into this situation before, I had to change the way we expose the API docs in ./docs/api: The directory now has sub-directories for each active API version. Therefore we need to change our scripts in the website repository to take this change into account so that we expose both API group version at https://fluxcd.io/flux/components/notification/api/. refs #436 Signed-off-by: Max Jonas Werner <[email protected]>
2 tasks
makkes
pushed a commit
that referenced
this issue
Mar 22, 2023
This commit bumps the Receiver API version to v1 in preparation of the Flux GitOps GA milestone (https://fluxcd.io/roadmap/#flux-gitops-ga-q1-2023). We are now actively maintaining two versions of the notification API group in parallel: v1 which currently only holds the Receiver kind and v1beta2 for all other kinds. Since we haven't run into this situation before, I had to change the way we expose the API docs in ./docs/api: The directory now has sub-directories for each active API version. Therefore we need to change our scripts in the website repository to take this change into account so that we expose both API group version at https://fluxcd.io/flux/components/notification/api/. refs #436 Signed-off-by: Max Jonas Werner <[email protected]>
makkes
pushed a commit
that referenced
this issue
Mar 23, 2023
This commit bumps the Receiver API version to v1 in preparation of the Flux GitOps GA milestone (https://fluxcd.io/roadmap/#flux-gitops-ga-q1-2023). We are now actively maintaining two versions of the notification API group in parallel: v1 which currently only holds the Receiver kind and v1beta2 for all other kinds. Since we haven't run into this situation before, I had to change the way we expose the API docs in ./docs/api: The directory now has sub-directories for each active API version. Therefore we need to change our scripts in the website repository to take this change into account so that we expose both API group version at https://fluxcd.io/flux/components/notification/api/. refs #436 Signed-off-by: Max Jonas Werner <[email protected]>
makkes
pushed a commit
to fluxcd/website
that referenced
this issue
Mar 23, 2023
With fluxcd/notification-controller#498 we're graduating the Receiver API group version to v1 and keeping all other kinds' version at v1beta2. Therefore we need to publish API docs for both version. refs fluxcd/notification-controller#436 Signed-off-by: Max Jonas Werner <[email protected]>
makkes
pushed a commit
to fluxcd/website
that referenced
this issue
Mar 23, 2023
With fluxcd/notification-controller#498 we're graduating the Receiver API group version to v1 and keeping all other kinds' version at v1beta2. Therefore we need to publish API docs for both version. refs fluxcd/notification-controller#436 Signed-off-by: Max Jonas Werner <[email protected]>
makkes
pushed a commit
to fluxcd/website
that referenced
this issue
Mar 23, 2023
With fluxcd/notification-controller#498 we're graduating the Receiver API group version to v1 and keeping all other kinds' version at v1beta2. Therefore we need to publish API docs for both version. refs fluxcd/notification-controller#436 Signed-off-by: Max Jonas Werner <[email protected]>
makkes
pushed a commit
to fluxcd/website
that referenced
this issue
Mar 23, 2023
With fluxcd/notification-controller#498 we're graduating the Receiver API group version to v1 and keeping all other kinds' version at v1beta2. Therefore we need to publish API docs for both version. refs fluxcd/notification-controller#436 Signed-off-by: Max Jonas Werner <[email protected]>
makkes
pushed a commit
that referenced
this issue
Mar 23, 2023
This commit bumps the Receiver API version to v1 in preparation of the Flux GitOps GA milestone (https://fluxcd.io/roadmap/#flux-gitops-ga-q1-2023). We are now actively maintaining two versions of the notification API group in parallel: v1 which currently only holds the Receiver kind and v1beta2 for all other kinds. Since we haven't run into this situation before, I had to change the way we expose the API docs in ./docs/api: The directory now has sub-directories for each active API version. Therefore we need to change our scripts in the website repository to take this change into account so that we expose both API group version at https://fluxcd.io/flux/components/notification/api/. refs #436 Signed-off-by: Max Jonas Werner <[email protected]>
makkes
pushed a commit
to fluxcd/website
that referenced
this issue
Mar 23, 2023
With fluxcd/notification-controller#498 we're graduating the Receiver API group version to v1 and keeping all other kinds' version at v1beta2. Therefore we need to publish API docs for both version. In addition to that we want the API navigation entry to appear at the bottom of the tree. To accomplish that the import script is now able to parse a weight parameter from imported markdown specs and put it into the front matter of the resulting file. refs fluxcd/notification-controller#436 Signed-off-by: Max Jonas Werner <[email protected]>
makkes
pushed a commit
to fluxcd/website
that referenced
this issue
Mar 23, 2023
With fluxcd/notification-controller#498 we're graduating the Receiver API group version to v1 and keeping all other kinds' version at v1beta2. Therefore we need to publish API docs for both version. In addition to that we want the API navigation entry to appear at the bottom of the tree. To accomplish that the import script is now able to parse a weight parameter from imported markdown specs and put it into the front matter of the resulting file. refs fluxcd/notification-controller#436 Signed-off-by: Max Jonas Werner <[email protected]>
makkes
pushed a commit
that referenced
this issue
Mar 24, 2023
This commit bumps the Receiver API version to v1 in preparation of the Flux GitOps GA milestone (https://fluxcd.io/roadmap/#flux-gitops-ga-q1-2023). We are now actively maintaining two versions of the notification API group in parallel: v1 which currently only holds the Receiver kind and v1beta2 for all other kinds. Since we haven't run into this situation before, I had to change the way we expose the API docs in ./docs/api: The directory now has sub-directories for each active API version. Therefore we need to change our scripts in the website repository to take this change into account so that we expose both API group version at https://fluxcd.io/flux/components/notification/api/. refs #436 Signed-off-by: Max Jonas Werner <[email protected]>
makkes
pushed a commit
that referenced
this issue
Mar 27, 2023
This commit bumps the Receiver API version to v1 in preparation of the Flux GitOps GA milestone (https://fluxcd.io/roadmap/#flux-gitops-ga-q1-2023). We are now actively maintaining two versions of the notification API group in parallel: v1 which currently only holds the Receiver kind and v1beta2 for all other kinds. Since we haven't run into this situation before, I had to change the way we expose the API docs in ./docs/api: The directory now has sub-directories for each active API version. Therefore we need to change our scripts in the website repository to take this change into account so that we expose both API group version at https://fluxcd.io/flux/components/notification/api/. refs #436 Signed-off-by: Max Jonas Werner <[email protected]>
15 tasks
makkes
pushed a commit
that referenced
this issue
Mar 30, 2023
This commit bumps the Receiver API version to v1 in preparation of the Flux GitOps GA milestone (https://fluxcd.io/roadmap/#flux-gitops-ga-q1-2023). We are now actively maintaining two versions of the notification API group in parallel: v1 which currently only holds the Receiver kind and v1beta2 for all other kinds. Since we haven't run into this situation before, I had to change the way we expose the API docs in ./docs/api: The directory now has sub-directories for each active API version. Therefore we need to change our scripts in the website repository to take this change into account so that we expose both API group version at https://fluxcd.io/flux/components/notification/api/. This change is implemented in fluxcd/website#1427. refs #436 Signed-off-by: Max Jonas Werner <[email protected]>
all done |
github-project-automation
bot
moved this from In Progress
to Since Last Dev Meeting
in Maintainers' Focus
Mar 30, 2023
makkes
pushed a commit
to fluxcd/website
that referenced
this issue
Mar 30, 2023
The following API types have been graduated to v1: - NC Receiver - KC Kustomization - SC GitRepository In addition to that we want the API navigation entries to appear at the bottom of the tree. To accomplish that the import script is now able to parse a weight parameter from imported markdown specs and put it into the front matter of the resulting file. refs fluxcd/notification-controller#436 Signed-off-by: Max Jonas Werner <[email protected]>
alekspog
pushed a commit
to alekspog/notification-controller
that referenced
this issue
Mar 30, 2023
This commit bumps the Receiver API version to v1 in preparation of the Flux GitOps GA milestone (https://fluxcd.io/roadmap/#flux-gitops-ga-q1-2023). We are now actively maintaining two versions of the notification API group in parallel: v1 which currently only holds the Receiver kind and v1beta2 for all other kinds. Since we haven't run into this situation before, I had to change the way we expose the API docs in ./docs/api: The directory now has sub-directories for each active API version. Therefore we need to change our scripts in the website repository to take this change into account so that we expose both API group version at https://fluxcd.io/flux/components/notification/api/. This change is implemented in fluxcd/website#1427. refs fluxcd#436 Signed-off-by: Max Jonas Werner <[email protected]>
makkes
pushed a commit
to fluxcd/website
that referenced
this issue
Mar 31, 2023
The following API types have been graduated to v1: - NC Receiver - KC Kustomization - SC GitRepository In addition to that we want the API navigation entries to appear at the bottom of the tree. To accomplish that the import script is now able to parse a weight parameter from imported markdown specs and put it into the front matter of the resulting file. refs fluxcd/notification-controller#436 Signed-off-by: Max Jonas Werner <[email protected]>
makkes
pushed a commit
to fluxcd/website
that referenced
this issue
Apr 5, 2023
The following API types have been graduated to v1: - NC Receiver - KC Kustomization - SC GitRepository In addition to that we want the API navigation entries to appear at the bottom of the tree. To accomplish that the import script is now able to parse a weight parameter from imported markdown specs and put it into the front matter of the resulting file. refs fluxcd/notification-controller#436 Signed-off-by: Max Jonas Werner <[email protected]>
makkes
pushed a commit
to fluxcd/website
that referenced
this issue
Apr 5, 2023
The following API types have been graduated to v1: - NC Receiver - KC Kustomization - SC GitRepository In addition to that we want the API navigation entries to appear at the bottom of the tree. To accomplish that the import script is now able to parse a weight parameter from imported markdown specs and put it into the front matter of the resulting file. refs fluxcd/notification-controller#436 Signed-off-by: Max Jonas Werner <[email protected]>
makkes
pushed a commit
to fluxcd/website
that referenced
this issue
Apr 5, 2023
The following API types have been graduated to v1: - NC Receiver - KC Kustomization - SC GitRepository In addition to that we want the API navigation entries to appear at the bottom of the tree. To accomplish that the import script is now able to parse a weight parameter from imported markdown specs and put it into the front matter of the resulting file. refs fluxcd/notification-controller#436 Signed-off-by: Max Jonas Werner <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Items to be reviewed plus any outstanding work required to bump the API to
v1
:notification.toolkit.fluxcd.io/v1
#498internal
package #499Depends on: #435
The text was updated successfully, but these errors were encountered: