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.

Sign up for GitHub

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

Jump to bottom

GA: Promote Receiver to notification.toolkit.fluxcd.io/v1 #436

Closed
20 tasks done
stefanprodan opened this issue Nov 2, 2022 · 1 comment
Closed
20 tasks done

GA: Promote Receiver to notification.toolkit.fluxcd.io/v1 #436

stefanprodan opened this issue Nov 2, 2022 · 1 comment
Assignees
@makkes
Milestone
Bootstrap GA

Comments

@stefanprodan
Copy link
Member

stefanprodan commented Nov 2, 2022 •
edited by makkes
Loading

Items to be reviewed plus any outstanding work required to bump the API to v1:

Depends on: #435
@stefanprodan stefanprodan added this to the GA milestone Nov 2, 2022
@stefanprodan stefanprodan mentioned this issue Nov 2, 2022
Closed
7 tasks
@pjbgf pjbgf modified the milestones: GA, Bootstrap GA Nov 2, 2022
@makkes makkes self-assigned this Mar 10, 2023
makkes added a commit that referenced this issue Mar 20, 2023
@makkes
fixes to the Receiver documentation
abc4991 
refs #436

Signed-off-by: Max Jonas Werner <max@e13.dev>
@makkes makkes mentioned this issue Mar 20, 2023
Merged
makkes pushed a commit that referenced this issue Mar 22, 2023
Introduce v1 API and bump Receiver version to v1
906243a 
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 <mail@makk.es>
@makkes makkes mentioned this issue Mar 22, 2023
Merged
2 tasks
makkes pushed a commit that referenced this issue Mar 22, 2023
Introduce v1 API and bump Receiver version to v1
8611b77 
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 <mail@makk.es>
makkes pushed a commit that referenced this issue Mar 23, 2023
Introduce v1 API and bump Receiver version to v1
1e6bd1e 
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 <mail@makk.es>
makkes pushed a commit to fluxcd/website that referenced this issue Mar 23, 2023
GA: adapt to n-c Receiver API graduating to v1
d09ee79 
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 <mail@makk.es>
@makkes makkes mentioned this issue Mar 23, 2023
Merged
makkes pushed a commit to fluxcd/website that referenced this issue Mar 23, 2023
GA: adapt to n-c Receiver API graduating to v1
a2370f9 
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 <mail@makk.es>
makkes pushed a commit to fluxcd/website that referenced this issue Mar 23, 2023
GA: adapt to n-c Receiver API graduating to v1
fceba74 
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 <mail@makk.es>
makkes pushed a commit to fluxcd/website that referenced this issue Mar 23, 2023
GA: adapt to n-c Receiver API graduating to v1
4e300f6 
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 <mail@makk.es>
makkes pushed a commit that referenced this issue Mar 23, 2023
Introduce v1 API and bump Receiver version to v1
83e946f 
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 <mail@makk.es>
makkes pushed a commit to fluxcd/website that referenced this issue Mar 23, 2023
GA: adapt to n-c Receiver API graduating to v1
818be4e 
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 <mail@makk.es>
makkes pushed a commit to fluxcd/website that referenced this issue Mar 23, 2023
GA: adapt to n-c Receiver API graduating to v1
d068deb 
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 <mail@makk.es>
makkes pushed a commit that referenced this issue Mar 24, 2023
Introduce v1 API and bump Receiver version to v1
93f2be6 
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 <mail@makk.es>
makkes pushed a commit that referenced this issue Mar 27, 2023
Introduce v1 API and bump Receiver version to v1
87de883 
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 <mail@makk.es>
@stefanprodan stefanprodan mentioned this issue Mar 30, 2023
Closed
15 tasks
makkes pushed a commit that referenced this issue Mar 30, 2023
Introduce v1 API and bump Receiver version to v1
ec03bd2 
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 <mail@makk.es>
@makkes
Copy link
Member

makkes commented Mar 30, 2023

all done

@makkes makkes closed this as completed Mar 30, 2023
makkes pushed a commit to fluxcd/website that referenced this issue Mar 30, 2023
GA: adapt to SC, NC and KC APIs graduating to v1
92cb3c0 
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 <mail@makk.es>
alekspog pushed a commit to alekspog/notification-controller that referenced this issue Mar 30, 2023
@alekspog
Introduce v1 API and bump Receiver version to v1
0e3f717 
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 <mail@makk.es>
makkes pushed a commit to fluxcd/website that referenced this issue Mar 31, 2023
GA: adapt to SC, NC and KC APIs graduating to v1
52b33f7 
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 <mail@makk.es>
makkes pushed a commit to fluxcd/website that referenced this issue Apr 5, 2023
GA: adapt to SC, NC and KC APIs graduating to v1
1e242c5 
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 <mail@makk.es>
makkes pushed a commit to fluxcd/website that referenced this issue Apr 5, 2023
GA: adapt to SC, NC and KC APIs graduating to v1
be0c3c5 
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 <mail@makk.es>
makkes pushed a commit to fluxcd/website that referenced this issue Apr 5, 2023
GA: adapt to SC, NC and KC APIs graduating to v1
3d32a85 
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 <mail@makk.es>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@makkes makkes

Labels
None yet
Projects
Maintainers' Focus
Archived in project
Milestone
Bootstrap GA
Development

No branches or pull requests
3 participants
@makkes @stefanprodan @pjbgf