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(send-signal): new function ContainersSendSignal to request the send-signal api's endpoint #295

Merged
merged 4 commits into from
Dec 28, 2022

Conversation

QuentinEscudierScalingo
Copy link
Contributor

@QuentinEscudierScalingo QuentinEscudierScalingo commented Dec 23, 2022

Fix #294

@QuentinEscudierScalingo QuentinEscudierScalingo force-pushed the feat/294/new_endpoint_send_signal branch from 9bcff82 to aeccae3 Compare December 23, 2022 13:38
@QuentinEscudierScalingo QuentinEscudierScalingo changed the title feat(send-signal): new function to request the send-signal api's endpoint feat(send-signal): new function to request ContainersSendSignal the send-signal api's endpoint Dec 23, 2022
@QuentinEscudierScalingo QuentinEscudierScalingo force-pushed the feat/294/new_endpoint_send_signal branch from 465773d to 9ed8faa Compare December 23, 2022 13:41
@QuentinEscudierScalingo QuentinEscudierScalingo changed the title feat(send-signal): new function to request ContainersSendSignal the send-signal api's endpoint feat(send-signal): new function ContainersSendSignal to request the send-signal api's endpoint Dec 23, 2022
Copy link
Member

@EtienneM EtienneM left a comment

Choose a reason for hiding this comment

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

Just a question otherwise LGTM

container.go Outdated
@@ -43,3 +43,18 @@ func (c *Client) ContainersStop(ctx context.Context, appName, containerID string

return nil
}

func (c *Client) ContainersSendSignal(ctx context.Context, app string, signal string, container string) error {
Copy link
Member

Choose a reason for hiding this comment

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

naming: I'm not completely convinced by the variable name container. Is it a name (e.g. web-1) or an ID (e.g. 5c9b95d201dcea2f34d496a3)? Depending on the answer I would name it containerName or containerID.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's a containerName, reasons why it's a docker_name instead of a docker_id is explained here https://github.com/Scalingo/api/pull/2096#discussion_r1057484461

Copy link
Member

@EtienneM EtienneM left a comment

Choose a reason for hiding this comment

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

I'm waiting for the merge of the API PR to finish the review here

@QuentinEscudierScalingo QuentinEscudierScalingo merged commit 0ed6ec4 into master Dec 28, 2022
@QuentinEscudierScalingo QuentinEscudierScalingo deleted the feat/294/new_endpoint_send_signal branch December 28, 2022 12:11
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.

New endpoint POST apps/id/containers/id/kill should be implemented
2 participants